<html><head><base href="x-msg://244/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">We have a question for the fb people.<div><br></div><div>We made the user ID in the user info endpoint id to be consistent with graph API.</div><div><br></div><div>We made user ID in the ID token/ introspection endpoint user_id because there is a desire to have long names.</div><div><br></div><div>Having the same thing called two things is obviously wrong.</div><div><br></div><div>So the question is should we be consistent with what Facebook has now or use something more descriptive because you want to move in that direction.</div><div><br></div><div>I am good ether way though have a slight preference for user_id because it is less ambiguous. </div><div><br></div><div>John B.</div><div><br></div><div><br></div><div><div><div>On 2011-07-30, at 12:56 AM, Mike Jones wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; 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-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1" style="page: WordSection1; "><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Thanks to much heavy lifting by Nat and John, we now have a first draft of the OpenID Connect Lite spec ready for you to review. The goal is that developers should be able to implement a minimal OpenID Connect implementation using only the information contained in this specification. (They’ll also have to implement Discovery and Registration if they want to enable interactions between parties that are not pre-configured to know about one another.) Please give it a read!<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">OpenID Connect Lite: <span class="Apple-converted-space"> </span><a href="http://openid.net/specs/openid-connect-lite-1_0.html" style="color: blue; text-decoration: underline; ">http://openid.net/specs/openid-connect-lite-1_0.html</a><o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Major changes relative to the former HTTP Redirect Binding spec are:<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in; "><span lang="EN" style="font-size: 10pt; font-family: Symbol; color: black; "><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></span></span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; ">Removed the<span class="Apple-converted-space"> </span></span><span lang="EN" style="font-size: 12pt; font-family: 'Courier New'; color: rgb(0, 51, 102); ">code</span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; "><span class="Apple-converted-space"> </span>flow. Only the<span class="Apple-converted-space"> </span></span><span lang="EN" style="font-size: 12pt; font-family: 'Courier New'; color: rgb(0, 51, 102); ">token</span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; "><span class="Apple-converted-space"> </span>flow is REQUIRED in Lite.<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in; "><span lang="EN" style="font-size: 10pt; font-family: Symbol; color: black; "><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></span></span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; ">Make requesting the<span class="Apple-converted-space"> </span></span><span lang="EN" style="font-size: 12pt; font-family: 'Courier New'; color: rgb(0, 51, 102); ">id_token</span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; "><span class="Apple-converted-space"> </span>be REQUIRED. The<span class="Apple-converted-space"> </span></span><span lang="EN" style="font-size: 12pt; font-family: 'Courier New'; color: rgb(0, 51, 102); ">id_token</span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; "><span class="Apple-converted-space"> </span>is treated as opaque.<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in; "><span lang="EN" style="font-size: 10pt; font-family: Symbol; color: black; "><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></span></span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; ">Make requesting the<span class="Apple-converted-space"> </span></span><span lang="EN" style="font-size: 12pt; font-family: 'Courier New'; color: rgb(0, 51, 102); ">token</span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; "><span class="Apple-converted-space"> </span>OPTIONAL, depending upon whether an Access Token for the UserInfo endpoint is needed or not.<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in; "><span lang="EN" style="font-size: 10pt; font-family: Symbol; color: black; "><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></span></span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; ">Dropped the<span class="Apple-converted-space"> </span></span><span lang="EN" style="font-size: 12pt; font-family: 'Courier New'; color: rgb(0, 51, 102); ">schema</span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; "><span class="Apple-converted-space"> </span>parameter to the Introspection endpoint, which was formerly a string with the value<span class="Apple-converted-space"> </span></span><span lang="EN" style="font-size: 12pt; font-family: 'Courier New'; color: rgb(0, 51, 102); ">user_id</span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; ">. This is unnecessary since the<span class="Apple-converted-space"> </span></span><span lang="EN" style="font-size: 12pt; font-family: 'Courier New'; color: rgb(0, 51, 102); ">id_token</span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; "><span class="Apple-converted-space"> </span>parameter already can be used to disambiguate the intended uses(s) of the endpoint.<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in; "><span lang="EN" style="font-size: 10pt; font-family: Symbol; color: black; "><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></span></span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; ">Dropped the requested audience from the Lite spec, which was formerly the identifier of the target audience of the response. This could be part of the Standard spec, but is an advanced scenario, and so not appropriate for Lite.<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in; "><span lang="EN" style="font-size: 10pt; font-family: Symbol; color: black; "><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></span></span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; ">Reference the Discovery and Registration specs, since they're needed for interaction between non-pre-configured parties (so that OpenID Connect installations can be Open).<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in; "><span lang="EN" style="font-size: 10pt; font-family: Symbol; color: black; "><span>·<span style="font: normal normal normal 7pt/normal 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></span></span><span lang="EN" style="font-size: 12pt; font-family: Verdana, sans-serif; color: black; ">Rearranged sections for readability.<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">This replaces the parts of the former HTTP Redirect Binding spec that were mandatory to implement. To complete the refactoring, the Messages spec and Standard spec still need to be produced from parts of the current Core, Framework, and HTTP Redirect Binding specs. All the specs under the old organization are still also live.<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "> Thanks all,<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "> -- Mike<o:p></o:p></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div></div>_______________________________________________<br>Openid-specs-ab mailing list<br><a href="mailto:Openid-specs-ab@lists.openid.net" style="color: blue; text-decoration: underline; ">Openid-specs-ab@lists.openid.net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" style="color: blue; text-decoration: underline; ">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br></div></span></blockquote></div><br></div></body></html>