refactor: change injection strategy for UdsPersonUserDetailsServiceImpl
Compare changes
If you received inactive project deletion emails on 4/30/25, you can ignore them. The projects named in those emails will NOT be deleted on 7/30/25. Some type of inactive project deletion will be implemented later this year, but you'll receive further communications before any deletions are scheduled.
UdsPersonUserDetailsServiceImpl
is not initialized automatically by either of the primary 'local-users' or 'preauth' Profiles. It's typically constructed by downstream projects manually (not by component scanning).
Registering more than 1 UserDetailsService
- say one for the uw-spring-security stack, and a different one for UdsPersonUserDetailsServiceImpl
- will result in ApplicationContext initialization errors as the Configuration classes provided in uw-spring-security-config expect 1 and only 1 UserDetailsService.
The recommended use now for UdsPersonUserDetailsServiceImpl
is to provide the needed UserDetailsService
by hand, not by automatic autowiring. If the 1 UserDetailsService provided by uw-spring-security is appropriate, it's easy to retrieve from the ApplicationContext; if an alternate one is required it can be constructed without registering it as a @Bean.