Yes! And I am going to bed for couple of hours of sleep today <img src="cid:B60@goomoji.gmail" style="margin-top: 0px; margin-right: 0.2ex; margin-bottom: 0px; margin-left: 0.2ex; vertical-align: middle; " goomoji="B60"><div>
<br></div><div>=nat<br><br><div class="gmail_quote">On Wed, Jul 6, 2011 at 3:45 AM, Mike Jones <span dir="ltr"><<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#002060">John has promised us updated discovery and dynamic client registration specs by the 3:00 Pacific call today, so no worries.
</span><span style="font-size:11.0pt;font-family:Wingdings;color:#002060">J</span><span style="font-size:11.0pt;color:#002060"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#002060"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;color:windowtext">From:</span></b><span style="font-size:10.0pt;color:windowtext"> <a href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a> [mailto:<a href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a>]
<b>On Behalf Of </b>George Fletcher<br>
<b>Sent:</b> Tuesday, July 05, 2011 11:20 AM<br>
<b>To:</b> Justin Richer</span></p><div><div></div><div class="h5"><br>
<b>Cc:</b> <a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a><br>
<b>Subject:</b> Re: [Openid-specs-ab] Updates to the UserInfo Endpoint spec<u></u><u></u></div></div><p></p>
</div>
</div><div><div></div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span>I'm fine not requiring a fixed path... however, with no convention, discovery becomes that much more critical. I don't see discovery being introduced for OAuth2 any time soon... which means
we are stuck with coding config tables of provider and endpoints. Not my favorite solution:)<br>
<br>
Thanks,<br>
George<br>
</span><br>
On 7/5/11 9:10 AM, Justin Richer wrote: <u></u><u></u></p>
<pre>+1 for showing an example endpoint but not requiring a specific path, if<u></u><u></u></pre>
<pre>for no other reason that not everybody can control their directory root.<u></u><u></u></pre>
<pre>Frameworks of all kinds have base routing that they add to things (like<u></u><u></u></pre>
<pre>Elgg's /pg/ prefix), and just like OAuth2 I'd want this to work in such<u></u><u></u></pre>
<pre>an environment. It's not just existing frameworks, though: I've even<u></u><u></u></pre>
<pre>tried to get a normal XRD endpoint on our server, and it's mired in all<u></u><u></u></pre>
<pre>kinds of red tape around who gets to put things on the root www server. <u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre> -- Justin<u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>On Sun, 2011-07-03 at 10:44 -0400, Nat Sakimura wrote:<u></u><u></u></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>+1 <u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre>On Sun, Jul 3, 2011 at 11:52 AM, Mike Jones<u></u><u></u></pre>
<pre><a href="mailto:Michael.Jones@microsoft.com" target="_blank"><Michael.Jones@microsoft.com></a> wrote:<u></u><u></u></pre>
<pre> OAuth doesn’t define any fixed paths. I don’t think we should<u></u><u></u></pre>
<pre> either, other than the discovery root(s).<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> --<u></u><u></u></pre>
<pre> Mike<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> From: <a href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">openid-specs-ab-bounces@lists.openid.net</a><u></u><u></u></pre>
<pre> [<a href="mailto:openid-specs-ab-bounces@lists.openid.net" target="_blank">mailto:openid-specs-ab-bounces@lists.openid.net</a>] On Behalf Of<u></u><u></u></pre>
<pre> Nat Sakimura<u></u><u></u></pre>
<pre> Sent: Friday, July 01, 2011 11:06 PM<u></u><u></u></pre>
<pre> To: George Fletcher<u></u><u></u></pre>
<pre> Cc: <a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a><u></u><u></u></pre>
<pre> Subject: Re: [Openid-specs-ab] Updates to the UserInfo<u></u><u></u></pre>
<pre> Endpoint spec<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> Does OAuth 2 define the fixed path? I was thinking /authorize<u></u><u></u></pre>
<pre> was just an example...<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> =nat<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> On Sat, Jul 2, 2011 at 9:21 AM, George Fletcher<u></u><u></u></pre>
<pre> <a href="mailto:gffletch@aol.com" target="_blank"><gffletch@aol.com></a> wrote:<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> Hi John,<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> I'm fine with the discovery spec defining the endpoints.. I<u></u><u></u></pre>
<pre> was thinking specifically of something like /userinfo, like<u></u><u></u></pre>
<pre> the OAuth2 spec defines /authorize and /token path portions of<u></u><u></u></pre>
<pre> the endpoint. Do we want that part variable on an<u></u><u></u></pre>
<pre> implementation by implementation basis?<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> Thanks,<u></u><u></u></pre>
<pre> George<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> On 7/1/11 6:39 PM, John Bradley wrote: <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> I think it is better to leave the path to the IdP. The<u></u><u></u></pre>
<pre> discovery document for the IdP will list the endpoint URL. <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> I would not assume that the host is necessarily the same as<u></u><u></u></pre>
<pre> the token or other endpoints.<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> John B.<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> On 2011-07-01, at 6:28 PM, George Fletcher wrote:<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> Hi,<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> I updated the text regarding the UserInfo request to say that<u></u><u></u></pre>
<pre> it is an OAuth2 protected resource supporting the Bearer Token<u></u><u></u></pre>
<pre> spec. I also changed the SHOULD to a MUST in the response text<u></u><u></u></pre>
<pre> requiring the JSON object to compile with the specified schema<u></u><u></u></pre>
<pre> if the schema parameter requests "openid". Also did some clean<u></u><u></u></pre>
<pre> ups in the referenced specs information.<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> One thing I just noticed is that we don't specify the path of<u></u><u></u></pre>
<pre> the UserInfo endpoint. Do we want to do so?<u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> Thanks,<u></u><u></u></pre>
<pre> George <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <openid-connect-userinfo-1_0.html>_______________________________________________<u></u><u></u></pre>
<pre> Openid-specs-ab mailing list<u></u><u></u></pre>
<pre> <a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><u></u><u></u></pre>
<pre> <a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> -- <u></u><u></u></pre>
<pre> Chief Architect AIM: gffletch<u></u><u></u></pre>
<pre> Identity Services Engineering Work: <a href="mailto:george.fletcher@teamaol.com" target="_blank">george.fletcher@teamaol.com</a><u></u><u></u></pre>
<pre> AOL Inc. Home: <a href="mailto:gffletch@aol.com" target="_blank">gffletch@aol.com</a><u></u><u></u></pre>
<pre> Mobile: <a href="tel:%2B1-703-462-3494" value="+17034623494" target="_blank">+1-703-462-3494</a> Blog: <a href="http://practicalid.blogspot.com" target="_blank">http://practicalid.blogspot.com</a><u></u><u></u></pre>
<pre> Office: <a href="tel:%2B1-703-265-2544" value="+17032652544" target="_blank">+1-703-265-2544</a> Twitter: <a href="http://twitter.com/gffletch" target="_blank">http://twitter.com/gffletch</a><u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> _______________________________________________<u></u><u></u></pre>
<pre> Openid-specs-ab mailing list<u></u><u></u></pre>
<pre> <a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><u></u><u></u></pre>
<pre> <a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> -- <u></u><u></u></pre>
<pre> Nat Sakimura (=nat)<u></u><u></u></pre>
<pre> <a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><u></u><u></u></pre>
<pre> <a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre> <u></u><u></u></pre>
<pre><u></u> <u></u></pre>
<pre><u></u> <u></u></pre>
<pre><u></u> <u></u></pre>
<pre>-- <u></u><u></u></pre>
<pre>Nat Sakimura (=nat)<u></u><u></u></pre>
<pre><a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><u></u><u></u></pre>
<pre><a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><u></u><u></u></pre>
</blockquote>
<pre><u></u> <u></u></pre>
<pre><u></u> <u></u></pre>
<pre>_______________________________________________<u></u><u></u></pre>
<pre>Openid-specs-ab mailing list<u></u><u></u></pre>
<pre><a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><u></u><u></u></pre>
<pre><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><u></u><u></u></pre>
<p class="MsoNormal"><u></u> <u></u></p>
</div></div></div>
</div>
<br>_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><br><a href="http://twitter.com/_nat_en">http://twitter.com/_nat_en</a><br>
</div>