Both endpoints deal with authorization of sorts. The reason why we have two is one is for direct client-server communication and the other one involves the end-user (a human).
EHL > -----Original Message----- > From: Dick Hardt [mailto:[email protected]] > Sent: Sunday, May 09, 2010 5:55 PM > To: Eran Hammer-Lahav > Cc: OAuth WG ([email protected]) > Subject: Re: [OAUTH-WG] User Endpoint > > I prefer authorization endpoint as it talks about the functionality of what > the > client gets from that endpoint. Delegation endpoint is another alternative. > User endpoint implies there must be a user present. I envision scenarios > where an identity agent deals with the authorization for the user and the > user is not involved. > > On 2010-05-09, at 2:15 PM, Eran Hammer-Lahav wrote: > > > I would like to rename the authorization endpoint to the user endpoint. > Any objections? > > > > EHL > > _______________________________________________ > > OAuth mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/oauth _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
