-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Implement Authorization Model / Service #43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @jgrandja, I would be happy to work on this issue. I have a question though. How would we derive a |
Thank you @watsta. The issue is yours.
Yes, this is correct. The |
An authorization server needs to maintain existing authorizations between a client and resource owner. For example, when a resource owner grants access to a client (to access its protected resources), the authorization server must persist certain data in order to validate the authorization grant flow until it completes.
For example, during an
authorization_code
grant flow, the authorization server must persist the following data:OAuth2AuthorizationRequest
client_id
Authentication.getName()
code
parameterOAuth2AccessToken
The initial implementation should provide an in-memory implementation of
OAuth2AuthorizationService
, similar toInMemoryOAuth2AuthorizedClientService
in thespring-security-oauth2-client
module.Implementation Requirements
InMemoryOAuth2AuthorizationService
should store in aMap
OAuth2Authorization
should be immutableOAuth2Authorization.attributes
should be used for storing data that is specific to an authorization grant, eg. authorizationcode
parameter,OAuth2AuthorizationRequest
, etc.class
andpublic
methodsSpecification References
4.1. Authorization Code Grant
The text was updated successfully, but these errors were encountered: