-
Notifications
You must be signed in to change notification settings - Fork 6k
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
AuthenticationConfiguration.lazyBean(AuthenticationManager.class) should honor @Primary if multiple candidates are available #3912
Labels
Milestone
Comments
Thanks for the report @cheppsn! I have scheduled this for 4.2 M1 |
Dropping from 4.2 as we are keeping this release focused on community contributions so the team can get Spring Security 5.0 out |
shazin
added a commit
to shazin/spring-security
that referenced
this issue
Nov 21, 2016
shazin
added a commit
to shazin/spring-security
that referenced
this issue
Dec 5, 2016
shazin
added a commit
to shazin/spring-security
that referenced
this issue
Dec 5, 2016
shazin
added a commit
to shazin/spring-security
that referenced
this issue
Dec 5, 2016
rwinch
pushed a commit
that referenced
this issue
Nov 14, 2018
jer051
pushed a commit
to jer051/spring-security
that referenced
this issue
Nov 21, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Using Spring Boot 1.3.4, Spring Security 4.0.4:
I encounter the following Exception for some (MockMvc) Tests that I want to run:
I tried to fix the issue by defining an
@Primary
annotated AuthenticationManager instance for my Test, but this has no effect. The reason being that theAuthenticationConfiguration.lazyBean()
Method does not honor@Primary
, if multiple candidates are found:The text was updated successfully, but these errors were encountered: