Hi Dick, The initial scope of the document was very limited to extending the existing Nested JWT to allow the enclosing JWT to have its own claims. Since then, it was clear that there are many use cases that need such a mechanism that requires more than just a simple nesting of JWTs. That's the reason I changed the name, to reflect the larger scope of this document.
I do not mind changing the name, if it makes sense. Would changing the name to Multi-Subject Nested JWT help address your concern? Regards, Rifaat On Tue, Jun 14, 2022 at 10:46 AM Dick Hardt <dick.ha...@gmail.com> wrote: > Hi Rifaat > > I'm suspecting there was a conversation on changing the name to > multi-subject JWT. Would you provide a pointer or short summary? > > I find the name concerning as I am looking at a very different concept > that would also be considered a multi-subject JWT. > > > My use case is where user accounts have been merged, and the issuer has > multiple "sub" claims for the same user and would like to include all the > values in the JWT to signal to the RP that the accounts have been merged. > > I was considering calling it "aka" and it would be an array of > identifiers. "aka" => Also Known As > > /Dick > > On Tue, Jun 14, 2022 at 5:25 AM Rifaat Shekh-Yusef < > rifaat.s.i...@gmail.com> wrote: > >> I have just submitted an updated version of the *Multi-Subject JWT* >> draft (formerly known as Nested JWT) with more details. >> I would appreciate any reviews and feedback on this version. >> https://datatracker.ietf.org/doc/html/draft-yusef-oauth-nested-jwt >> >> Regards, >> Rifaat >> >> _______________________________________________ >> OAuth mailing list >> OAuth@ietf.org >> https://www.ietf.org/mailman/listinfo/oauth >> >
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
