-
Notifications
You must be signed in to change notification settings - Fork 6k
Allow the ability to configure AuthoritiesMapper in Reactive OAuth2Login #8324
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
@choweiyuan Indeed, Would you be interested in submitting a PR for this? |
@choweiyuan You can also consider a Delegation-based strategy with OAuth2UserService. The provided link demonstrates a sample for Servlet but the same strategy can be applied on the Reactive side as well. |
I'm interested in submitting a PR for this if it is ok for you @jgrandja Just one question, would the default Or would the user have to manually configure the authentication manager if they want to provide a custom authority mapper ? |
Thanks for the offer @antonin-arquey! The issue is yours.
Yes, please go with this option. |
Allow the configuration of a custom GrantedAuthorityMapper for reactive OAuth2Login - Add setter in OidcAuthorizationCodeReactiveAuthenticationManager and OAuth2LoginReactiveAuthenticationManager - Use an available GrantedAuthorityMapper bean to configure the default ReactiveAuthenticationManager Fixes spring-projectsgh-8324
Summary
I'd like the ability to modify Reactive OAuth2Login's authoritiesMapper.
Actual Behavior
Can't find a suitable API to configure this. There's an equivalent for the Servlet HttpSecurity but not for Reactive equivalent.
Digging into the source code further seem to suggest that OAuth2LoginAuthenticationProvider (Servlet) have setAuthoritiesMapper, and OidcAuthorizationCodeReactiveAuthenticationManager (Reactive) does not have setAuthoritiesMapper
Expected Behavior
I expect I can do something similar for Reactive OAuth2Login
Configuration
Servlet HttpSecurity
Reactive
Version
5.2.1.RELEASE
Sample
Will provide soon if it gives further clarity
The text was updated successfully, but these errors were encountered: