According to section "6 Refreshing an Access Token" (-13.txt), client when
making a request for exchanging a refresh token for an access token has to
include its authentication credentials, and the "authorization server MUST
validate the client credentials".
How can this be done if a client is an application that can't have a client
secret?
The authorization code grant does require client authentication (per section
4.1):
(D) The client requests an access token from the authorization
server's token endpoint by authenticating using its client
credentials, and includes the authorization code received in the
previous step.
It appears that the clients that cannot keep its secret cannot use (be issued)
the refresh tokens.
Zachary
-----Original Message-----
From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of
Marius Scurtescu
Sent: Monday, April 04, 2011 2:30 PM
To: Kris Selden
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] Flowchart for legs of OAuth
On Mon, Apr 4, 2011 at 10:47 AM, Kris Selden <kris.sel...@gmail.com> wrote:
> A typical iPhone app cannot be shipped with a client secret and rightly or
> wrongly users expect to only have to enter their credentials once.
>
> What is the best profile to use for an app that can't have a client secret
> and needs a refresh token or a long lived access token?
The authorization code grant, aka web server flow.
The spec is misleading in this respect IMO.
Marius
_______________________________________________
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
