Maintaining both information in the JWT is IMHO valuable since it gives you some information about the security properties. Needless to say that there is a substantial difference between a self-created JWT and a JWT from a third party the relying party has some confidence in.
Why Google has an old implementation and whether they are planning to update their code remains to be seen. More importantly, however, is why you argue that the subject claim has to be optional. Ciao Hannes Ps: I also noticed in the examples that all URIs have their URI scheme missing. While that might be OK I am not entirely sure... On 03/11/2014 04:08 PM, Antonio Sanso wrote: > > On Mar 11, 2014, at 3:53 PM, Hannes Tschofenig <hannes.tschofe...@gmx.net> > wrote: > >> Thanks for clarifying. >> >> I took a quick look at the Google API and it seems that in their use >> case the client creates the JWT and consequently the subject and the >> issue would actually be the same. I suspect that this is the reason why >> they omitted the subject. > > agreed that is why in my mail I said the subject might overlap with the > issuer. > The subject in the google case is still called with its obsolete name (prn) > and it is actually listed as ‘additional claims’ hence not mandatory. > > regards > > antonio > >> >> Could you explain why you would like to omit the subject claim in the JWT? >> >> Ciao >> Hannes >> >> PS: Your feedback on the draft-ietf-oauth-jwt-bearer-07 spec is timely >> since we are about to finish all three assertion specs. >> >> >> On 03/11/2014 03:56 PM, Antonio Sanso wrote: >>> hi Hannes, >>> >>> I am aware of the 2 documents, >>> >>> I might be wrong but >>> http://tools.ietf.org/html/draft-ietf-oauth-jwt-bearer-07 is also about >>> Authorization Grant Processing (this is the part I do use in my >>> implementation ) and not only Client Authentication Processing. >>> >>> Just my 0.02 $ but this seems to be a place where different implementer >>> have the same issue :) >>> >>> regards >>> >>> antonio >>> >>> On Mar 11, 2014, at 3:36 PM, Hannes Tschofenig <hannes.tschofe...@gmx.net> >>> wrote: >>> >>>> Hi Manfred, Hi Antonio, >>>> >>>> Note that there are two documents that talk about the JWT and you guys >>>> might be looking at the wrong document. >>>> >>>> The main JWT document (see >>>> http://tools.ietf.org/html/draft-ietf-oauth-json-web-token-18) defines >>>> the subject claim as optional (see Section 4.1.2). >>>> >>>> The JWT bearer assertion document (see >>>> http://tools.ietf.org/html/draft-ietf-oauth-jwt-bearer-07) does indeed >>>> define it as mandatory but that's intentional since the purpose of the >>>> spec is to authenticate the client (or the resource owner for an >>>> authorization grant). >>>> >>>> The assertion documents are used for interworking with "legacy" identity >>>> infrastructure (such as SAML federations). >>>> >>>> So, are you sure you are indeed looking at the right document? >>>> >>>> Ciao >>>> Hannes >>>> >>>> >>>> On 03/11/2014 03:13 PM, Antonio Sanso wrote: >>>>> hi *, >>>>> >>>>> JSON Web Token (JWT) Profile section 3 [0] explicitely says >>>>> >>>>> The JWT MUST contain a "sub" (subject) claim >>>>> >>>>> >>>>> Now IMHO there are cases where having the sub is either not needed or >>>>> redundant (since it might overlap with the issuer).\ >>>>> >>>>> As far as I can see “even Google” currently violates this spec [1] ( I >>>>> know that this doesn’t matter, just wanted to bring a real use case >>>>> scenario). >>>>> >>>>> WDYT might the “sub” be optional in some situation? >>>>> >>>>> regards >>>>> >>>>> antonio >>>>> >>>>> [0] http://tools.ietf.org/html/draft-ietf-oauth-jwt-bearer-07#section-3 >>>>> [1] https://developers.google.com/accounts/docs/OAuth2ServiceAccount >>>>> >>>>> >>>>> _______________________________________________ >>>>> OAuth mailing list >>>>> OAuth@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/oauth >>>>> >>>> >>> >> >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
