-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Closed
Labels
in: oauth2An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)status: ideal-for-contributionAn issue that we actively are looking for someone to help us withAn issue that we actively are looking for someone to help us withtype: enhancementA general enhancementA general enhancement
Milestone
Description
Expected Behavior
Headers added to the request via .headers((headers) -> populateTokenRequestHeaders(grantRequest, headers))
of the WebClient
should be customizable so the application can add additional headers or customize the default set of headers provided by AbstractWebClientReactiveOAuth2AccessTokenResponseClient
.
Current Behavior
Currently, the request can only be customized by providing a custom WebClient
and registering an ExchangeFilterFunction
. This limits the application to only the current ClientRequest
, possibly requiring parsing and mutating the request after it has already been built, with the inability to access the current AbstractOAuth2AuthorizationGrantRequest
.
Context
See gh-10042
Metadata
Metadata
Assignees
Labels
in: oauth2An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)status: ideal-for-contributionAn issue that we actively are looking for someone to help us withAn issue that we actively are looking for someone to help us withtype: enhancementA general enhancementA general enhancement