<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I think it is better to leave the path to the IdP. The discovery document for the IdP will list the endpoint URL.<div><br></div><div>I would not assume that the host is necessarily the same as the token or other endpoints.</div><div><br></div><div>John B.<br><div><div>On 2011-07-01, at 6:28 PM, George Fletcher wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">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</font>
</div>
<span><openid-connect-userinfo-1_0.html></span>_______________________________________________<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<br></blockquote></div><br></div></body></html>