Skip to content

DefaultReactiveOAuth2AuthorizedClientManager should default ServerWebExchange #7390

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.

Sign up for GitHub

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

Jump to bottom
Closed
jgrandja opened this issue Sep 6, 2019 · 0 comments
Closed

DefaultReactiveOAuth2AuthorizedClientManager should default ServerWebExchange #7390

jgrandja opened this issue Sep 6, 2019 · 0 comments
Assignees
@jgrandja
Labels
in: oauth2 An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose) type: enhancement A general enhancement
Milestone
5.2.0

Comments

@jgrandja
Copy link
Contributor

jgrandja commented Sep 6, 2019

DefaultReactiveOAuth2AuthorizedClientManager should default the ServerWebExchange from the Reactor Context if it's not already provided in OAuth2AuthorizeRequest.attributes.
@jgrandja jgrandja self-assigned this Sep 6, 2019
@jgrandja jgrandja added in: oauth2 An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose) type: enhancement A general enhancement labels Sep 6, 2019
@jgrandja jgrandja added this to the 5.2.0 milestone Sep 6, 2019
@jgrandja jgrandja mentioned this issue Sep 26, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jgrandja jgrandja

Labels
in: oauth2 An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose) type: enhancement A general enhancement
Projects
None yet
Milestone
5.2.0
Development

No branches or pull requests
1 participant
@jgrandja