+1 <br><br><div class="gmail_quote">On Sun, Jul 3, 2011 at 11:52 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 lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#002060">OAuth doesn’t define any fixed paths. I don’t think we should either, other than the discovery root(s).<u></u><u></u></span></p>
<p class="MsoNormal"><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"> -- Mike<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> <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>Nat Sakimura<br>
<b>Sent:</b> Friday, July 01, 2011 11:06 PM<br>
<b>To:</b> George Fletcher<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></span></p><div><div></div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Does OAuth 2 define the fixed path? I was thinking /authorize was just an example...<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">=nat<u></u><u></u></p>
<div>
<p class="MsoNormal">On Sat, Jul 2, 2011 at 9:21 AM, George Fletcher <<a href="mailto:gffletch@aol.com" target="_blank">gffletch@aol.com</a>> wrote:<u></u><u></u></p>
<div>
<p class="MsoNormal"><span>Hi John,<br>
<br>
I'm fine with the discovery spec defining the endpoints.. I was thinking specifically of something like /userinfo, like the OAuth2 spec defines /authorize and /token path portions of the endpoint. Do we want that part variable on an implementation by implementation
basis?<br>
<br>
Thanks,<br>
George</span><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><br>
On 7/1/11 6:39 PM, John Bradley wrote: <u></u><u></u></p>
<p class="MsoNormal">I think it is better to leave the path to the IdP. The discovery document for the IdP will list the endpoint URL.
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I would not assume that the host is necessarily the same as the token or other endpoints.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">John B.<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">On 2011-07-01, at 6:28 PM, George Fletcher wrote:<u></u><u></u></p>
</div>
<p class="MsoNormal"><br>
<br>
<u></u><u></u></p>
<div>
<p class="MsoNormal"><span>Hi,<br>
<br>
I updated the text regarding the UserInfo request to say that it is an OAuth2 protected resource supporting the Bearer Token spec. I also changed the SHOULD to a MUST in the response text requiring the JSON object to compile with the specified schema if the
schema parameter requests "openid". Also did some clean ups in the referenced specs information.<br>
<br>
One thing I just noticed is that we don't specify the path of the UserInfo endpoint. Do we want to do so?<br>
<br>
Thanks,<br>
George</span> <u></u><u></u></p>
</div>
<p class="MsoNormal"><openid-connect-userinfo-1_0.html>_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">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><u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<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" 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" 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>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">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><u></u><u></u></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <br>
Nat Sakimura (=nat)<br>
<a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br>
<a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><u></u><u></u></p>
</div>
</div></div></div>
</div>
</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>