cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-4673) [OAuth2] Add requestedScope as a parameter to getPreauthorizedToken
Date Tue, 04 Dec 2012 22:16:59 GMT


Sergey Beryozkin commented on CXF-4673:

Not sure about it either :-). I guess the idea with using the pre-authorized tokens (which
I implemented based on the comments I saw at the oauth2 list) in general in that the resource
owner works with a dedicated UI which allows the end user to select which registered clients
can be allocated a pre-authorized token (or this can be done somehow differently) - this token
will have its properties set, that is the client requested scope if any is basically ignored;
the requested scope is only useful when the token is created right now, for the provider to
compare the requested scope and the approved scope; with the preauthorized token whatever
the user pre-authorized is then set in stone until the user decides to revoke it, change it,

Does it sound reasonable to you ?
> [OAuth2] Add requestedScope as a parameter to getPreauthorizedToken
> -------------------------------------------------------------------
>                 Key: CXF-4673
>                 URL:
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-RS Security
>    Affects Versions: 2.7.0
>            Reporter: Steven Tippetts
> When using pre-authorized tokens I need the requested scope to be able to create the
> Please change the OAuthDataProvider interface to include:
> {code}
> ServerAccessToken getPreauthorizedToken(Client client,
>                                         UserSubject subject,
>                                         String grantType, 
>                                         List<String> requestedScope)
>     throws OAuthServiceException;
> {code}
> And change and to pass the
requestedScope variable in to getPreauthorizedToken.
> Thanks.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message