|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||
java.lang.Objectorg.springframework.security.oauth2.provider.DefaultAuthorizationRequestManager
public class DefaultAuthorizationRequestManager
Default implementation of AuthorizationRequestManager which validates grant types and scopes and fills in
scopes with the default values from the client if they are missing.
| Constructor Summary | |
|---|---|
DefaultAuthorizationRequestManager(ClientDetailsService clientDetailsService)
|
|
| Method Summary | |
|---|---|
AuthorizationRequest |
createAuthorizationRequest(Map<String,String> parameters)
Create a new AuthorizationRequest extracting all the needed information from the incoming parameter map. |
void |
validateParameters(Map<String,String> parameters,
ClientDetails clientDetails)
Validate the parameters provided by the client. |
| Methods inherited from class java.lang.Object |
|---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Constructor Detail |
|---|
public DefaultAuthorizationRequestManager(ClientDetailsService clientDetailsService)
| Method Detail |
|---|
public AuthorizationRequest createAuthorizationRequest(Map<String,String> parameters)
AuthorizationRequestManagerAuthorizationRequest extracting all the needed information from the incoming parameter map.
Typical implementations would load the client details from the client id provided and validate the grant type and
scopes, populating any fields in the request that are known only to the authorization server.
createAuthorizationRequest in interface AuthorizationRequestManagerparameters - the parameters in the request
public void validateParameters(Map<String,String> parameters,
ClientDetails clientDetails)
AuthorizationRequestManager
Validate the parameters provided by the client. Called by the AuthorizationEndpoint and also by the
TokenEndpoint before a response is sent back to the client. Note that during an authorization code flow
both endpoints will call this method, but the TokenEndpoint in that case has very little if anything to validate
since all the parameters neeeded for the access token were provided to the AuthorizationEndpoint.
Implementations should at a minimum check that the scope values requested are legal for the client.
validateParameters in interface AuthorizationRequestManagerparameters - the request parametersclientDetails - the client requesting the token
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||