Skip to content

Add RestOperations implementation of OAuth2AccessTokenResponseClient #5547

Closed
@jgrandja

Description

@jgrandja

The current (and default) implementation of OAuth2AccessTokenResponseClient for the authorization_code grant is NimbusAuthorizationCodeTokenResponseClient, which leverages the Nimbus HTTP Client internally.

We should provide a new implementation of OAuth2AccessTokenResponseClient for the authorization_code grant named DefaultAuthorizationCodeTokenResponseClient that uses RestOperations for requesting to the Token Endpoint.

Additionally, DefaultAuthorizationCodeTokenResponseClient should expose setRestOperations(restOperations) method to allow user's the ability to supply a pre-configured RestOperations, which can provide the user the capability to add custom parameters and/or headers if required.

DefaultAuthorizationCodeTokenResponseClient should be the new default in OAuth2LoginConfigurer and OAuth2ClientConfigurer.

Related #5601

Metadata

Metadata

Assignees

Labels

in: oauth2An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)type: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions