Spring Security InitializeUserDetailsBeanManagerConfigurer#InitializeUserDetailsManagerConfigurer.getBeanOrNull optimization

Expected Behavior When multiple UserDetailsServices found, throw NoUniqueBeanDefinitionException.

Current Behavior When I registered more than one UserDetailsService, InitializeUserDetailsBeanManagerConfigurer#InitializeUserDetailsManagerConfigurer.getBeanOrNull returned null.

Comment From: rwinch

Please provide more details around when and why you would want this to happen.

Note there are many times a user may want to provide multiple beans for Authentication and not want this to fail. If we have multiple UserDetailsService instances, we still want to check if there is a single AuthenticationProvider and use that. If we have multiple AuthenticationProvider instances, we still want to be able to check if there is a single AuthenticationManager.

Comment From: spring-projects-issues

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Comment From: spring-projects-issues

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.