<div dir="ltr">Now tracking it as <a href="https://bitbucket.org/openid/connect/issue/955/">https://bitbucket.org/openid/connect/issue/955/</a><div><br></div><div>Will discuss this in twenty minutes. </div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2014-08-28 13:27 GMT+09:00 John Bradley <span dir="ltr"><<a href="mailto:ve7jtb@ve7jtb.com" target="_blank">ve7jtb@ve7jtb.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto"><div>I thought there was some plan to relaunch as cloud names. Perhaps they are separate. I expect Markus knows<br><br>Sent from my iPhone</div><div><div class="h5"><div><br>On Aug 27, 2014, at 11:24 PM, Mike Jones <<a href="mailto:Michael.Jones@microsoft.com" target="_blank">Michael.Jones@microsoft.com</a>> wrote:<br>
<br></div><blockquote type="cite"><div>
<div>
<div style="font-family:Calibri,sans-serif;font-size:11pt">2 are advertised at <a href="http://xri.org" target="_blank">xri.org</a><br>
</div>
</div>
<div dir="ltr">
<hr>
<span style="font-family:Calibri,sans-serif;font-size:11pt;font-weight:bold">From:
</span><span style="font-family:Calibri,sans-serif;font-size:11pt"><a href="mailto:sakimura@gmail.com" target="_blank">Nat Sakimura</a></span><br>
<span style="font-family:Calibri,sans-serif;font-size:11pt;font-weight:bold">Sent:
</span><span style="font-family:Calibri,sans-serif;font-size:11pt">8/27/2014 7:21 PM</span><br>
<span style="font-family:Calibri,sans-serif;font-size:11pt;font-weight:bold">To:
</span><span style="font-family:Calibri,sans-serif;font-size:11pt"><a href="mailto:ve7jtb@ve7jtb.com" target="_blank">John Bradley</a></span><br>
<span style="font-family:Calibri,sans-serif;font-size:11pt;font-weight:bold">Cc:
</span><span style="font-family:Calibri,sans-serif;font-size:11pt"><a href="mailto:ejay@mgi1.com" target="_blank">Edmund Jay</a>;
<a href="mailto:Michael.Jones@microsoft.com" target="_blank">Mike Jones</a>; <a href="mailto:markus.sabadello@gmail.com" target="_blank">
Markus Sabadello</a>; <a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a></span><br>
<span style="font-family:Calibri,sans-serif;font-size:11pt;font-weight:bold">Subject:
</span><span style="font-family:Calibri,sans-serif;font-size:11pt">Re: [Openid-specs-ab] Some comments on OpenID 2.0 to OpenID Connect Migration spec</span><br>
<br>
</div>
<div>
<div>So, how many I-Brokers are there now? <br>
<br>
=nat via iPhone</div>
<div><br>
Aug 28, 2014 10:20、John Bradley <<a href="mailto:ve7jtb@ve7jtb.com" target="_blank">ve7jtb@ve7jtb.com</a>> のメッセージ:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div>In principal that is what we created the JRD for in the XRI WG. </div>
<div><br>
</div>
<div>The question is more what NuStar is doing with the transition to cloud names and what roll Connect will have for whatever replaces iBrokers. <br>
<br>
Sent from my iPhone</div>
<div><br>
On Aug 27, 2014, at 6:38 PM, Edmund Jay <<a href="mailto:ejay@mgi1.com" target="_blank">ejay@mgi1.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div style="color:#000;background-color:#fff;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:10pt">
<div><span>Shouldn't iss and sub contain values from the OpenID Connect provider? Unless, of course the OpenID Connect provider is
<a href="https://xri.net/" target="_blank">https://xri.net</a></span></div>
<div><br>
</div>
<div style="color:rgb(0,0,0);font-size:13px;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;background-color:transparent;font-style:normal">
<span>XRI resolution returns the OpenID 2.0 provider that is configured by the i-name owner.</span></div>
<div style="color:rgb(0,0,0);font-size:13px;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;background-color:transparent;font-style:normal">
<span><br>
</span></div>
<div style="color:rgb(0,0,0);font-size:13px;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;background-color:transparent;font-style:normal">
<span style="background-color:transparent">So in regards to the spec, we need to determine whether it's possible to get the OpenID Connect iss from a GET request to
<a href="https://xri.net/(some" target="_blank">https://xri.net/(some</a> i-name) with an </span><span style="background-color:transparent">Accept header of application/json.</span><br>
</div>
<div style="color:rgb(0,0,0);font-size:13px;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;background-color:transparent;font-style:normal">
<span style="background-color:transparent"><br>
</span></div>
<div style="color:rgb(0,0,0);font-size:13px;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;background-color:transparent;font-style:normal">
<span style="background-color:transparent">If not, then we need to think of another scheme for verification of XRI OpenID 2.0 Identifiers.</span></div>
<div style="color:rgb(0,0,0);font-size:13px;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;background-color:transparent;font-style:normal">
<br>
</div>
<div style="color:rgb(0,0,0);font-size:13px;font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;background-color:transparent;font-style:normal">
<span><br>
</span></div>
<div><br>
</div>
<div style="font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:10pt">
<div style="font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:12pt">
<div dir="ltr">
<hr size="1">
<font face="Arial"><b><span style="font-weight:bold">From:</span></b> Mike Jones <<a href="mailto:Michael.Jones@microsoft.com" target="_blank">Michael.Jones@microsoft.com</a>><br>
<b><span style="font-weight:bold">To:</span></b> Markus Sabadello <<a href="mailto:markus.sabadello@gmail.com" target="_blank">markus.sabadello@gmail.com</a>>; Nat Sakimura <<a href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>>
<br>
<b><span style="font-weight:bold">Cc:</span></b> "<a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a>" <<a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a>>
<br>
<b><span style="font-weight:bold">Sent:</span></b> Wednesday, August 27, 2014 12:18 PM<br>
<b><span style="font-weight:bold">Subject:</span></b> Re: [Openid-specs-ab] Some comments on OpenID 2.0 to OpenID Connect Migration spec<br>
</font></div>
<div><br>
<div>
<div>
<div>
<div><span style="font-size:11.0pt">I suspect that the “iss” would be
<a rel="nofollow" shape="rect" href="https://xri.net/" target="_blank">https://xri.net</a> and the “sub” would be the i-number, such as “</span><b>=!91F2.8153.F600.AE24</b><span style="font-size:11.0pt">”.</span></div>
<div><span style="font-size:11.0pt"> </span></div>
<div><span style="font-size:11.0pt">I guess the real question we haven’t explicitly asked is whether
<a href="http://xri.net" target="_blank">xri.net</a> can/will become an OpenID Connect provider – which is what would make migration possible. What are your thoughts on this, Markus?</span></div>
<div><span style="font-size:11.0pt"> </span></div>
<div><span style="font-size:11.0pt"> -- Mike</span></div>
<div><span style="font-size:11.0pt"> </span></div>
<div><br>
<br>
</div>
<div>
<div><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> Markus Sabadello [<a href="mailto:markus.sabadello@gmail.com" target="_blank">mailto:markus.sabadello@gmail.com</a>]
<br clear="none">
<b>Sent:</b> Wednesday, August 27, 2014 11:50 AM<br clear="none">
<b>To:</b> Nat Sakimura<br clear="none">
<b>Cc:</b> Mike Jones; <a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a><br clear="none">
<b>Subject:</b> Re: [Openid-specs-ab] Some comments on OpenID 2.0 to OpenID Connect Migration spec</span></div>
<div> </div>
<div>
<div>
<div>
<div>
<div style="margin-bottom:12.0pt">Yes to me it feels right to just say that openid2_id is the OpenID 2.0 Claimed Identifier.</div>
</div>
<div style="margin-bottom:12.0pt">What I don't fully understand yet is whether in the OIDC world the Authorization Endpoint would be hosted 1. at
<a rel="nofollow" shape="rect" href="https://xri.net/some/path" target="_blank">https://xri.net/some/path</a>, or 2. individually by the i-brokers.</div>
</div>
<div style="margin-bottom:12.0pt">If 1., then for the migration spec I think no discovery step would be needed, since the issuer would always be
<a rel="nofollow" shape="rect" href="https://xri.net/" target="_blank">https://xri.net</a> anyway, no?</div>
</div>
<div>What would the "iss" and "sub" fields be for an ID token issued for an XRI?</div>
<div>
<div style="margin-bottom:12.0pt"><br clear="none">
Markus</div>
</div>
</div>
</div>
<div>
<div>
<div style="margin-bottom:12.0pt"> </div>
<div>
<div>On Mon, Aug 25, 2014 at 6:25 PM, Nat Sakimura <<a rel="nofollow" shape="rect" href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>> wrote:</div>
<div>
<div>Having said that, it is probably better to have the canonical XRI itself in the openid2_id. </div>
<div>
<div>Note though, Canonical ID only exists for XRI. In all other cases, it is the Verified Claimed ID. </div>
</div>
<div>
<div>In XRI's case, the value of the Canonical ID is used as the verified Claimed Identifier. </div>
</div>
<div>
<div>So, in general, just stating that openid2_id is OpenID 2.0 Identifier suffices. </div>
</div>
<div>
<div> </div>
</div>
<div>
<div>We would however have to add text to the discovery portion. </div>
</div>
<div>
<div> </div>
</div>
<div>
<div>In http(s) case, there is no change. </div>
</div>
<div>
<div>For XRI case, it has to be prefixed by <a rel="nofollow" shape="rect" href="https://xri.net/" target="_blank">
https://xri.net/</a>. </div>
</div>
<div>
<div> </div>
</div>
<div>
<div>My question to Markus at this point is how realistic that
<a rel="nofollow" shape="rect" href="http://xri.net/" target="_blank">xri.net</a> will implement this feature. </div>
</div>
<div>
<div>Do you have any idea? </div>
</div>
<div>
<div> </div>
</div>
<div>
<div>Nat</div>
</div>
</div>
<div>
<div style="margin-bottom:12.0pt"> </div>
<div>
<div>2014-08-26 0:31 GMT+09:00 Nat Sakimura <<a rel="nofollow" shape="rect" href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>>:</div>
<div>
<div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div> </div>
<div>
<div>That would actually complicate 90% of the cases where openid2_id is a http(s) URI. </div>
<div>
<div>And I probably was a bit sleepy when I wrote the last response. </div>
</div>
<div>
<div>It is not xri://<a rel="nofollow" shape="rect" href="http://xri.net/" target="_blank">xri.net/</a> obviously. </div>
</div>
<div>
<div>I meant <a rel="nofollow" shape="rect" href="https://xri.net/" target="_blank">
https://xri.net/</a> etc. so that the discovery process would be uniform to the RPs. </div>
</div>
</div>
<div>
<div style="margin-bottom:12.0pt"> </div>
<div>
<div>2014-08-25 23:44 GMT+09:00 Mike Jones <<a rel="nofollow" shape="rect" href="mailto:Michael.Jones@microsoft.com" target="_blank">Michael.Jones@microsoft.com</a>>:</div>
<div>
<div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div> </div>
<div>
<div>
<div><span style="font-size:11.0pt">I prefer the alternative that Markus is suggesting, in which we always use the OpenID 2.0 canonical identifier as the openid2_id claim value. In fact, I would consider adding his example,
in which this claim value is shown:</span></div>
<div>"openid2_id": "<b>=!91F2.8153.F600.AE24</b>"</div>
<div><span style="font-size:11.0pt"> </span></div>
<div><span style="font-size:11.0pt">We should then describe how to prefix this value to perform discovery, rather than removing the prefix.</span></div>
<div><span style="font-size:11.0pt"> </span></div>
<div><span style="font-size:11.0pt"> -- Mike</span></div>
<div><span style="font-size:11.0pt"> </span></div>
<div><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt">
<a rel="nofollow" shape="rect" href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">
openid-specs-ab-bounces@lists.openid.net</a> [mailto:<a rel="nofollow" shape="rect" href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a>]
<b>On Behalf Of </b>Nat Sakimura<br clear="none">
<b>Sent:</b> Monday, August 25, 2014 7:26 AM<br clear="none">
<b>To:</b> Markus Sabadello<br clear="none">
<b>Cc:</b> <a rel="nofollow" shape="rect" href="mailto:openid-specs-ab@lists.openid.net" target="_blank">
openid-specs-ab@lists.openid.net</a><br clear="none">
<b>Subject:</b> Re: [Openid-specs-ab] Some comments on OpenID 2.0 to OpenID Connect Migration spec</span></div>
<div>
<div>
<div> </div>
<div>
<div>
<div>Thanks Markus, </div>
</div>
<div>
<div> </div>
</div>
<div>
<div>I created tickets based on these comments. </div>
</div>
<div>
<div> </div>
</div>
<div>
<div>This particular one is: <a rel="nofollow" shape="rect" href="https://bitbucket.org/openid/connect/issue/950/migration-te-4-xri-portion-needs-change-by" target="_blank">https://bitbucket.org/openid/connect/issue/950/migration-te-4-xri-portion-needs-change-by</a></div>
</div>
<div>
<div> </div>
</div>
<div>
<div>For the relying party, I think it would be relatively straight forward to strip xri:// from openid2_id if they stored XRI as pure CanonicalID and causes less confusion than trying to figure out the type of openid2_id
by sniffing if it starts from "=" or "!" or "@" etc. </div>
</div>
<div>
<div> </div>
</div>
<div>
<div>This comment thus seem to imply that we should add some text in section 7, e.g., adding: </div>
</div>
<div>
<div> </div>
</div>
<div>
<div>If the OpenID 2.0 Identifier starts with xri://<a rel="nofollow" shape="rect" href="http://xri.net/" target="_blank">xri.net/</a> then the relying party MUST extract the Canonical XRI by stripping "xri://<a rel="nofollow" shape="rect" href="http://xri.net/" target="_blank">xri.net/</a>"
from the beginning of the OpenID 2.0 Identifier. </div>
</div>
<div>
<div> </div>
</div>
<div>
<div>What do you think? </div>
</div>
<div>
<div> </div>
</div>
<div>
<div>Nat</div>
</div>
<div>
<div> </div>
<div>
<div>2014-08-23 21:36 GMT+09:00 Markus Sabadello <<a rel="nofollow" shape="rect" href="mailto:markus.sabadello@gmail.com" target="_blank">markus.sabadello@gmail.com</a>>:</div>
<div>
<div>In section 4:</div>
<div>"For XRI, OpenID 2.0 Identifier MUST be created as <a rel="nofollow" shape="rect" href="https://xri.net/" target="_blank">
https://xri.net/</a> concatenated with the user’s verified XRI without the xri:// scheme. "</div>
<div>The problem with this I think is that in OpenID 2.0, for an XRI the Claimed Identifier is the pure CanonicalID (I-Number), without https:// or xri:// scheme. For example, an RP might have
<b>=!91F2.8153.F600.AE24</b> as the Claimed Identifier (openid2_id) for a user in its database.</div>
<div style="margin-bottom:12.0pt">So I think in section 4, we should either not say anything specific at all about XRI, or say something like this:<br clear="none">
<br clear="none">
"For XRI, OpenID 2.0 Identifier MUST be the content of the <CanonicalID> element, as specified in [OpenID.2.0]"</div>
</div>
<div>
<div>Then an example ID Token would be:</div>
<pre>{</pre>
<pre> "iss": "?? not sure",</pre>
<pre> "sub": "?? not sure",</pre>
<pre> "aud": "s6BhdRkqt3",</pre>
<pre> "nonce": "n-0S6_WzA2Mj",</pre>
<pre> "exp": 1311281970,</pre>
<pre> "iat": 1311280970,</pre>
<pre> "openid2_id": "<b>=!91F2.8153.F600.AE24</b>"</pre>
<pre>}</pre>
<div>But then I can see that obtaining an "iss" as described in sections 2 and 6 won't work.</div>
</div>
</div>
<div><br clear="none">
<br clear="none">
<br clear="all">
</div>
<div>
<div> </div>
</div>
<div>-- <br clear="none">
Nat Sakimura (=nat)</div>
<div>
<div>Chairman, OpenID Foundation<br clear="none">
<a rel="nofollow" shape="rect" href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br clear="none">
@_nat_en</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<div>
<div>
<div><br clear="none">
<br clear="all">
</div>
<div>
<div> </div>
</div>
<div>-- <br clear="none">
Nat Sakimura (=nat)</div>
<div>
<div>Chairman, OpenID Foundation<br clear="none">
<a rel="nofollow" shape="rect" href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br clear="none">
@_nat_en</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<div>
<div>
<div><br clear="none">
<br clear="all">
</div>
<div>
<div> </div>
</div>
<div>-- <br clear="none">
Nat Sakimura (=nat)</div>
<div>
<div>Chairman, OpenID Foundation<br clear="none">
<a rel="nofollow" shape="rect" href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br clear="none">
@_nat_en</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div> </div>
</div>
</div>
</div>
</div>
<br>
<div>_______________________________________________<br clear="none">
Openid-specs-ab mailing list<br clear="none">
<a shape="rect" href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br clear="none">
<a shape="rect" href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br clear="none">
</div>
<br>
<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Openid-specs-ab mailing list</span><br>
<span><a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a></span><br>
<span><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a></span><br>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div></blockquote></div></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Nat Sakimura (=nat)<div>Chairman, OpenID Foundation<br><a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>
@_nat_en</div>
</div>