Open arnonuem opened 5 years ago
The registration filter needs a UserDetailsManager
(which is an extending interface of UserDetailsService
) since that's the interface that provides the mutating operations, specifically
The registration filter is optional if your users are provisioned elsewhere. So, one solution could be to not use that filter and only use the RequestBodyLoginFilter
, which delegates to the usual AuthenticationManager
which in turn only requires a UserDetailsService
.
Instead of an InMemoryUserDetailsManager i am using a UserDetailsService implementation since i have some extravagant logic besides just tapping into a database.
This is the error i get:
Could a solution be that the RegistrationFilter in the SinglePageAppConfigurer also allows a UserDetailsService instead of just a UserDetailsManager?