[Openid-specs-ab] New Core: 184.108.40.206 RECOMMENDs the same Access Token but...
Michael.Jones at microsoft.com
Mon Oct 21 16:55:50 UTC 2013
This, and the related text about the multiple ID Tokens possible with the hybrid flow are on the agenda to discuss today.
The text about the ID Token in http://openid.net/specs/openid-connect-core-1_0.html#HybridIDToken2 is more important, actually, containing minimum requirements that the issuer and subject be the same, etc.
From: openid-specs-ab-bounces at lists.openid.net [mailto:openid-specs-ab-bounces at lists.openid.net] On Behalf Of Nat Sakimura
Sent: Monday, October 21, 2013 9:38 AM
To: openid-specs-ab at lists.openid.net
Subject: [Openid-specs-ab] New Core: 220.127.116.11 RECOMMENDs the same Access Token but...
The new core recommends the following. This seems to be a new text introduced in the new core.
18.104.22.168. Access Token
If an Access Token is returned from both the Authorization Endpoint and from the Token Endpoint, which is the case with the response_type values code token and code id_token token, it is RECOMMENDED that their values be the same.
Is this true? I feel like the opposite is true. The reason for getting Access Token from both the AuthZ Endpoint and the Token Endpoint is that they have different security characteristics: The later is more secure and thus trusted. So, there is a value in differentiating between them. e.g. the former has lesser expiry time as well as lesser permission.
I feel like it should be as follows:
22.214.171.124. Access Token
If an Access Token is returned from both the Authorization Endpoint and from the Token Endpoint, which is the case with the response_type values code token and code id_token token, it is RECOMMENDED that their values be different. The access token returned from Authorization Endpoint is more vulnerable to various attack so that it has less trust than that returned from the Token Endpoint. Thus, the Server MAY give lesser permission and shorter life time for the Access Token that is returned from the Authorization Endpoint.
Section 2.3 has bunch of bugs which was quite clear in how to fix, but this one was not that obvious so I am asking.
Nat Sakimura (=nat)
Chairman, OpenID Foundation
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openid-specs-ab