<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><base href="x-msg://1806/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I am in favour of having JWT and id_token consistent, as long as we are not changing the semantic of user_id and only the claim name.<div><br></div><div>As I stated earlier the user_id claim was an attempt to match facebooks claims. I don't think that logic panned out in the end. </div><div><br></div><div>Better to change it once to be consistent. For a transition period IdP could send both prn and user_id to make the change easier. </div><div><br></div><div>I don't care much if the claim is called prn or sub they both are used for the same thing in other specs that couldn't agree on what to call them.</div><div><br></div><div>Leaving it prn is fine with me unless people overwhelmingly prefer sub.</div><div><br></div><div>John B.</div><div><br><div><div>On 2012-12-19, at 1:46 PM, <<a href="mailto:Axel.Nennker@telekom.de">Axel.Nennker@telekom.de</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">+1 for prn in both specs<o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> </span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "><span class="Apple-converted-space"> </span><a href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a> [mailto:openid-<a href="mailto:specs-ab-bounces@lists.openid.net">specs-ab-bounces@lists.openid.net</a>]<span class="Apple-converted-space"> </span><b>On Behalf Of<span class="Apple-converted-space"> </span></b>Breno de Medeiros<br><b>Sent:</b><span class="Apple-converted-space"> </span>Wednesday, December 19, 2012 5:19 PM<br><b>To:</b><span class="Apple-converted-space"> </span>Mike Jones<br><b>Cc:</b><span class="Apple-converted-space"> </span><a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a><br><b>Subject:</b><span class="Apple-converted-space"> </span>Re: [Openid-specs-ab] Inconsistency between user_id and prn claims - notice of upcoming breaking change<o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><o:p> </o:p></div><div><div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">While the rename represents another breaking change to Google's early implementation and will require additional transition planning, I can't say that I am against the universal usage of 'prn'. I expect that developers and deployers will appreciate being able to expect 'prn' in all their interactions.<o:p></o:p></span></div></div><div><p class="MsoNormal" style="margin: 0cm 0cm 12pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 10pt; font-family: Arial, sans-serif; "> </span></p><div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">On Tue, Dec 18, 2012 at 11:51 AM, Mike Jones <<a href="mailto:Michael.Jones@microsoft.com" target="_blank" style="color: purple; text-decoration: underline; ">Michael.Jones@microsoft.com</a>> wrote:<o:p></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">Just to remove any ambiguity, was your +1 for "prn" or "sub", Torsten?<br><span style="color: rgb(136, 136, 136); "><br><span class="hoenzb"> -- Mike</span></span><o:p></o:p></span></div><div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 10pt; font-family: Arial, sans-serif; "><br>-----Original Message-----<br>From:<span class="Apple-converted-space"> </span><a href="mailto:openid-specs-ab-bounces@lists.openid.net" style="color: purple; text-decoration: underline; ">openid-specs-ab-bounces@lists.openid.net</a><span class="Apple-converted-space"> </span>[mailto:<a href="mailto:openid-specs-ab-bounces@lists.openid.net" style="color: purple; text-decoration: underline; ">openid-specs-ab-bounces@lists.openid.net</a>] On Behalf Of Torsten Lodderstedt<br>Sent: Tuesday, December 18, 2012 10:54 AM<br>To: Justin Richer<br>Cc:<span class="Apple-converted-space"> </span><a href="mailto:openid-specs-ab@lists.openid.net" style="color: purple; text-decoration: underline; ">openid-specs-ab@lists.openid.net</a><br>Subject: Re: [Openid-specs-ab] Inconsistency between user_id and prn claims - notice of upcoming breaking change<br><br>+1<br><br>Am 18.12.2012 16:10, schrieb Justin Richer:<br>> +1, though I prefer "sub" over "prn" as it reads better.<br>><br>> -- Justin<br>><br>> On 12/18/2012 03:37 AM, Vladimir Dzhuvinov / NimbusDS wrote:<br>>> +1 for prn. Consistency with OAuth JWT assertion makes good sense.<br>>><br>>> Thanks,<br>>><br>>> Vladimir<br>>><br>>> --<br>>> Vladimir Dzhuvinov :<span class="Apple-converted-space"> </span><a href="http://www.NimbusDS.com" target="_blank" style="color: purple; text-decoration: underline; ">www.NimbusDS.com</a><span class="Apple-converted-space"> </span>:<span class="Apple-converted-space"> </span><a href="mailto:vladimir@nimbusds.com" style="color: purple; text-decoration: underline; ">vladimir@nimbusds.com</a><br>>><br>>><br>>> -------- Original Message --------<br>>> Subject: [Openid-specs-ab] Inconsistency between user_id and prn<br>>> claims<br>>> - notice of upcoming breaking change<br>>> From: Mike Jones <<a href="mailto:Michael.Jones@microsoft.com" style="color: purple; text-decoration: underline; ">Michael.Jones@microsoft.com</a>><br>>> Date: Tue, December 18, 2012 1:05 am<br>>> To: "<a href="mailto:openid-specs-ab@lists.openid.net" style="color: purple; text-decoration: underline; ">openid-specs-ab@lists.openid.net</a>"<br>>> <<a href="mailto:openid-specs-ab@lists.openid.net" style="color: purple; text-decoration: underline; ">openid-specs-ab@lists.openid.net</a>><br>>> Cc: "<a href="mailto:openid-connect-interop@googlegroups.com" style="color: purple; text-decoration: underline; ">openid-connect-interop@googlegroups.com</a>"<br>>> <<a href="mailto:openid-connect-interop@googlegroups.com" style="color: purple; text-decoration: underline; ">openid-connect-interop@googlegroups.com</a>><br>>><br>>> Mitre and Microsoft implementers have both recently independently<br>>> pointed out that an ID Token is not currently usable as an OAuth JWT<br>>> Assertion because it uses the “user_id” claim to identify the subject<br>>> of the token, rather than the “prn” (principal) claim, as specified<br>>> in the OAuth JWT Assertion spec. This inconsistency is already<br>>> causing real problems/limitations for implementations. See<br>>><span class="Apple-converted-space"> </span><a href="http://hg.openid.net/connect/issue/687" target="_blank" style="color: purple; text-decoration: underline; ">http://hg.openid.net/connect/issue/687</a><span class="Apple-converted-space"> </span>for more background on the issue.<br>>> This was discussed on the working group call today and it was<br>>> decided that while changing the “user_id” claim name now would be<br>>> painful, it would be more painful over time to keep having<br>>> implementer’s try to work around this inconsistency when they need to<br>>> use an ID Token as an OAuth JWT assertion. Therefore, we decided<br>>> that the specs should be changed so that an ID Token is a legal OAuth<br>>> JWT Assertion. The simplest way to do this would be to change all<br>>> uses of the claim name “user_id” to “prn”. Only the syntax would<br>>> change – not the meaning of the claim.<br>>> The other potential solution that was discussed was to change<br>>> both the names “user_id” and “prn” to “sub” (subject). While being a<br>>> (somewhat) more meaningful name, using “prn” was preferred because it<br>>> will involve a change only to the Connect specs – not also to the JWT<br>>> and OAuth JWT Assertion specs.<br>>> The participants in the working group call decided that we<br>>> should make this change, but we wanted to give clear notice to the<br>>> working group and interop participants of this upcoming breaking<br>>> change. If you would like to propose an alternative solution to the<br>>> inconsistency, please do so before the Thursday OpenID Connect call.<br>>> We plan to include this change in the upcoming implementer’s drafts.<br>>> -- Mike<br>>> _______________________________________________<br>>> Openid-specs-ab mailing list<br>>><span class="Apple-converted-space"> </span><a href="mailto:Openid-specs-ab@lists.openid.net" style="color: purple; text-decoration: underline; ">Openid-specs-ab@lists.openid.net</a><br>>><span class="Apple-converted-space"> </span><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank" style="color: purple; text-decoration: underline; ">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>>> _______________________________________________<br>>> Openid-specs-ab mailing list<br>>><span class="Apple-converted-space"> </span><a href="mailto:Openid-specs-ab@lists.openid.net" style="color: purple; text-decoration: underline; ">Openid-specs-ab@lists.openid.net</a><br>>><span class="Apple-converted-space"> </span><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank" style="color: purple; text-decoration: underline; ">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>><br>> _______________________________________________<br>> Openid-specs-ab mailing list<br>><span class="Apple-converted-space"> </span><a href="mailto:Openid-specs-ab@lists.openid.net" style="color: purple; text-decoration: underline; ">Openid-specs-ab@lists.openid.net</a><br>><span class="Apple-converted-space"> </span><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank" style="color: purple; text-decoration: underline; ">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br><br>_______________________________________________<br>Openid-specs-ab mailing list<br><a href="mailto:Openid-specs-ab@lists.openid.net" style="color: purple; text-decoration: underline; ">Openid-specs-ab@lists.openid.net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank" style="color: purple; text-decoration: underline; ">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>_______________________________________________<br>Openid-specs-ab mailing list<br><a href="mailto:Openid-specs-ab@lists.openid.net" style="color: purple; text-decoration: underline; ">Openid-specs-ab@lists.openid.net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank" style="color: purple; text-decoration: underline; ">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><o:p></o:p></span></div></div></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 10pt; font-family: Arial, sans-serif; "><br><br clear="all"><o:p></o:p></span></div><div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 10pt; font-family: Arial, sans-serif; "> </span></div></div><p class="MsoNormal" style="margin: 0cm 0cm 12pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-size: 10pt; font-family: Arial, sans-serif; ">--<span class="Apple-converted-space"> </span><br>--Breno<o:p></o:p></span></p></div></div></div>_______________________________________________<br>Openid-specs-ab mailing list<br><a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br>http://lists.openid.net/mailman/listinfo/openid-specs-ab</div></blockquote></div><br></div></body></html>