<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">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>
</font><br>
On 7/5/11 9:10 AM, Justin Richer wrote:
<blockquote cite="mid:1309871415.28669.3.camel@ground" type="cite">
<pre wrap="">+1 for showing an example endpoint but not requiring a specific path, if
for no other reason that not everybody can control their directory root.
Frameworks of all kinds have base routing that they add to things (like
Elgg's /pg/ prefix), and just like OAuth2 I'd want this to work in such
an environment. It's not just existing frameworks, though: I've even
tried to get a normal XRD endpoint on our server, and it's mired in all
kinds of red tape around who gets to put things on the root www server.
-- Justin
On Sun, 2011-07-03 at 10:44 -0400, Nat Sakimura wrote:
</pre>
<blockquote type="cite">
<pre wrap="">+1
On Sun, Jul 3, 2011 at 11:52 AM, Mike Jones
<a class="moz-txt-link-rfc2396E" href="mailto:Michael.Jones@microsoft.com"><Michael.Jones@microsoft.com></a> wrote:
OAuth doesn’t define any fixed paths. I don’t think we should
either, other than the discovery root(s).
--
Mike
From: <a class="moz-txt-link-abbreviated" href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a>
[<a class="moz-txt-link-freetext" href="mailto:openid-specs-ab-bounces@lists.openid.net">mailto:openid-specs-ab-bounces@lists.openid.net</a>] On Behalf Of
Nat Sakimura
Sent: Friday, July 01, 2011 11:06 PM
To: George Fletcher
Cc: <a class="moz-txt-link-abbreviated" href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>
Subject: Re: [Openid-specs-ab] Updates to the UserInfo
Endpoint spec
Does OAuth 2 define the fixed path? I was thinking /authorize
was just an example...
=nat
On Sat, Jul 2, 2011 at 9:21 AM, George Fletcher
<a class="moz-txt-link-rfc2396E" href="mailto:gffletch@aol.com"><gffletch@aol.com></a> wrote:
Hi John,
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?
Thanks,
George
On 7/1/11 6:39 PM, John Bradley wrote:
I think it is better to leave the path to the IdP. The
discovery document for the IdP will list the endpoint URL.
I would not assume that the host is necessarily the same as
the token or other endpoints.
John B.
On 2011-07-01, at 6:28 PM, George Fletcher wrote:
Hi,
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.
One thing I just noticed is that we don't specify the path of
the UserInfo endpoint. Do we want to do so?
Thanks,
George
<openid-connect-userinfo-1_0.html>_______________________________________________
Openid-specs-ab mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
--
Chief Architect AIM: gffletch
Identity Services Engineering Work: <a class="moz-txt-link-abbreviated" href="mailto:george.fletcher@teamaol.com">george.fletcher@teamaol.com</a>
AOL Inc. Home: <a class="moz-txt-link-abbreviated" href="mailto:gffletch@aol.com">gffletch@aol.com</a>
Mobile: +1-703-462-3494 Blog: <a class="moz-txt-link-freetext" href="http://practicalid.blogspot.com">http://practicalid.blogspot.com</a>
Office: +1-703-265-2544 Twitter: <a class="moz-txt-link-freetext" href="http://twitter.com/gffletch">http://twitter.com/gffletch</a>
_______________________________________________
Openid-specs-ab mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
--
Nat Sakimura (=nat)
<a class="moz-txt-link-freetext" href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/_nat_en">http://twitter.com/_nat_en</a>
--
Nat Sakimura (=nat)
<a class="moz-txt-link-freetext" href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/_nat_en">http://twitter.com/_nat_en</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Openid-specs-ab mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
</pre>
</blockquote>
<br>
</body>
</html>