[Openid-specs-ab] JWT claims in signed UserInfo responses
sakimura at gmail.com
Wed Nov 6 19:28:45 UTC 2013
Right, it is not an assertion that you reuse for something.
Having said that, sub is only scoped to iss, and when storing the userinfo
result at the client, it probably is a good idea to store iss with it.
The reason for including aud also is not to use it as a token, but as a
metadata to prevent the accidental leak.
2013/11/6 Torsten Lodderstedt <torsten at lodderstedt.net>
> I'm getting confused. I thought the reason to encrypt/sign UserInfo is to
> implement end2end message security. I don't see the UserInfo response as
> another kind of assertion intended to be passed around. The ID Token is
> intended for that purpose, right?
> Therefore I don't see a need to add aud or iss claims to the UserInfo
> Am 06.11.2013 02:29, schrieb Nat Sakimura:
>> And perhaps aud as well to prevent an accidental transfer to a third
>> It is not a MUST but still is a good practice.
>> =nat via iPhone
>> Nov 6, 2013 1:56、"Vladimir Dzhuvinov / NimbusDS" <vladimir at nimbusds.com>
>> Hi guys,
>>> For UserInfo responses encoded as JWTs - which of the standard JWT
>>> claims, apart from the mandatory "sub", do you choose to include?
>>> It appears to me that in order for the UserInfo to be suitable for
>>> passing around as a JWT it should include at least the "iss" claim.
>>> Vladimir Dzhuvinov : www.NimbusDS.com : vladimir at nimbusds.com
>>> Openid-specs-ab mailing list
>>> Openid-specs-ab at lists.openid.net
>> Openid-specs-ab mailing list
>> Openid-specs-ab at lists.openid.net
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
Nat Sakimura (=nat)
Chairman, OpenID Foundation
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openid-specs-ab