<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>
<div style="font-family:Calibri,sans-serif; font-size:11pt">Wonderful - thanks!<br>
<br>
</div>
</div>
<hr>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">From:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">Roland Hedberg</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">Sent:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">1/4/2013 4:47 AM</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">To:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">openid-connect-interop@googlegroups.com</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">Cc:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">openid-specs-ab@lists.openid.net</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">Subject:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">Re: December 27, 2012 OpenID Connect Release</span><br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi !<br>
<br>
The code running on the test site (<a href="http://openidtest.uninett.no/">http://openidtest.uninett.no/</a>)<br>
and my own OP at xenosmilus2.umdc.umu.se are now updated to comply with the these changes.<br>
<br>
29 dec 2012 kl. 02:09 skrev Mike Jones <Michael.Jones@microsoft.com>:<br>
<br>
> 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.)<br>
> <br>
> Other updates were:<br>
> · 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.<br>
> · A new “tos_url” registration parameter was added so that the terms of service can be specified separately from the usage policy.<br>
> · Clarified that “jwk_url” and “jwk_encryption_url” refer to documents containing JWK Sets - not single JWK keys.<br>
> <br>
> Implementers need to apply these name changes to their code:<br>
> · user_id -> sub<br>
> · prn -> sub<br>
> · user_id_types_supported -> subject_types_supported<br>
> · user_id_type -> subject_type<br>
> · acrs_supported -> acr_values_supported<br>
> · alg -> kty (in JWKs)<br>
> <br>
> See the Document History section of each specification for more details about the changes made.<br>
> <br>
> 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.<br>
> <br>
> The new specification versions are:<br>
> · <a href="http://openid.net/specs/openid-connect-basic-1_0-22.html">http://openid.net/specs/openid-connect-basic-1_0-22.html</a><br>
> · <a href="http://openid.net/specs/openid-connect-implicit-1_0-05.html">
http://openid.net/specs/openid-connect-implicit-1_0-05.html</a><br>
> · <a href="http://openid.net/specs/openid-connect-messages-1_0-14.html">
http://openid.net/specs/openid-connect-messages-1_0-14.html</a><br>
> · <a href="http://openid.net/specs/openid-connect-standard-1_0-15.html">
http://openid.net/specs/openid-connect-standard-1_0-15.html</a><br>
> · <a href="http://openid.net/specs/openid-connect-discovery-1_0-11.html">
http://openid.net/specs/openid-connect-discovery-1_0-11.html</a><br>
> · <a href="http://openid.net/specs/openid-connect-registration-1_0-13.html">
http://openid.net/specs/openid-connect-registration-1_0-13.html</a><br>
> · <a href="http://openid.net/specs/openid-connect-session-1_0-10.html">http://openid.net/specs/openid-connect-session-1_0-10.html</a><br>
> <br>
> -- Mike<br>
<br>
-- Roland<br>
------------------------------------------------------<br>
Roland Hedberg<br>
IT Architect/Senior Researcher<br>
ICT Services and System Development (ITS) <br>
Umeĺ University <br>
SE-901 87 Umeĺ, Sweden <br>
Phone +46 90 786 68 44<br>
Mobile +46 70 696 68 44 <br>
<a href="http://www.its.umu.se">www.its.umu.se</a> <br>
<br>
</div>
</span></font>
</body>
</html>