[Openid-specs-ab] December 27, 2012 OpenID Connect Release

Torsten Lodderstedt torsten at lodderstedt.net
Sat Dec 29 09:44:52 UTC 2012

Hi Mike,

great work!

I took a first glance on the new offline_access scope and noticed the following typos:

Section 2.1.1

"token that grants access the End-User's UserInfo endpoint" 

should read

"token that grants access to the End-User's UserInfo endpoint"

Section 6

I also assume the sentence 

"When offline access is requested, a prompt, parameter value of consent MUST be used."

should read

"When offline access is requested a prompt parameter value of consent MUST be used."

I've also got a question regarding the forced user consent:

Why is the requirement for user consent relaxed for native apps?


Am 29.12.2012 um 02:09 schrieb Mike Jones <Michael.Jones at microsoft.com>:

> New versions of the OpenID Connect specifications have been released resolving numerous open issues raised by the working group.  The most significant change is changing the name of the “user_id” claim to “sub” (subject) so that ID Tokens conform to the OAuth JWT Bearer Profile specification, and so they can be used as OAuth assertions.  (Also, see the related coordinated change to the OAuth JWT specifications.)  A related enhancement was extending our use of the “aud” (audience) claim to allow ID Tokens to have multiple audiences.  Also, a related addition was defining the “azp” (authorized party) claim to allow implementers to experiment with this proposed functionality.  (This is a slightly more general form of the “cid” claim that Google and Nat Sakimura had proposed.)
> Other updates were:
> ·        The “offline_access” scope value was defined to request that a refresh token be returned when using the code flow that can be used to obtain an access token granting access to the user’s UserInfo endpoint even when the user is not present.
> ·        A new “tos_url” registration parameter was added so that the terms of service can be specified separately from the usage policy.
> ·        Clarified that “jwk_url” and “jwk_encryption_url” refer to documents containing JWK Sets - not single JWK keys.
> Implementers need to apply these name changes to their code:
> ·        user_id -> sub
> ·        prn -> sub
> ·        user_id_types_supported -> subject_types_supported
> ·        user_id_type -> subject_type
> ·        acrs_supported -> acr_values_supported
> ·        alg -> kty (in JWKs)
> See the Document History section of each specification for more details about the changes made.
> This release is part of a coordinated release of JOSE, OAuth, and OpenID Connect specifications.  You can read about the other releases here:  JOSE Release Notes, OAuth Release Notes.
> The new specification versions are:
> ·        http://openid.net/specs/openid-connect-basic-1_0-22.html
> ·        http://openid.net/specs/openid-connect-implicit-1_0-05.html
> ·        http://openid.net/specs/openid-connect-messages-1_0-14.html
> ·        http://openid.net/specs/openid-connect-standard-1_0-15.html
> ·        http://openid.net/specs/openid-connect-discovery-1_0-11.html
> ·        http://openid.net/specs/openid-connect-registration-1_0-13.html
> ·        http://openid.net/specs/openid-connect-session-1_0-10.html
>                                                             -- Mike
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-ab
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20121229/13e8208b/attachment-0001.html>

More information about the Openid-specs-ab mailing list