-
Notifications
You must be signed in to change notification settings - Fork 6k
Introduce a Map-based AuthenticationManagerResolver #6762
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
Labels
Milestone
Comments
i can't find |
Good catch, @clevertension. I've updated the description. |
jzheaux
added a commit
to jzheaux/spring-security
that referenced
this issue
Sep 5, 2019
jzheaux
added a commit
that referenced
this issue
Dec 16, 2021
jzheaux
added a commit
that referenced
this issue
Jan 25, 2022
jzheaux
added a commit
that referenced
this issue
Jan 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Recently, #6722 introduced a contract for resolving an
AuthenticationManager
via some context, like a request.A natural implementation for this would be one that contained a
Map<RequestMatcher, AuthenticationManager>
and selected theAuthenticationManager
from the configuredMap
.This aligns with other request-matching API implementations like
DelegatingAuthenticationEntryPoint
andRequestMatcherDelegatingAccessDeniedHandler
.The text was updated successfully, but these errors were encountered: