+1 on delegation. This conveys the purpose nicely - I think these endpoints are always to verify that there is a currently logged in user for the purpose of delegation. "User" seems a bit vague - "user agent" seems more appropriate if we want to reference that this occurs in a browser.
Also note that "token endpoint" is confusing given the fact that you can get a token without ever talking to the token endpoint (in the User Agent flow). Don't have great suggestions, but wanted to point out. On Mon, May 10, 2010 at 5:18 AM, Richer, Justin P. <jric...@mitre.org>wrote: > So long as we keep some language in the text that this is the endpoint > where the authorization by the user takes place, this change makes sense to > me. People coming from OAuth 1 and similar schemes are going to be looking > for the "authorization" part, I think. > > -- Justin > > ________________________________________ > From: oauth-boun...@ietf.org [oauth-boun...@ietf.org] On Behalf Of Eran > Hammer-Lahav [e...@hueniverse.com] > Sent: Sunday, May 09, 2010 5:15 PM > To: OAuth WG (oauth@ietf.org) > Subject: [OAUTH-WG] User Endpoint > > I would like to rename the authorization endpoint to the user endpoint. Any > objections? > > EHL > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth >
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
