Using JdbcUserDetailsManager and Native UserDetailsService

Question

I learned about Spring Security, and I do not fully understand if I should use the JdbcUserDetailsManager or the custom implementation of UserDetailsService . I use a database to store users.

I don’t understand what JdbcUserDetailsManager gives you, besides a lot of methods, which I’m not sure what I want to use? What if you have checks, etc.? Do you wrap it in your own implementation of UserDetailsService ?

I mean, would you skip this manager class in your application. Is it better to create your own?

Answer 1

There are some differences:

• UserDetailsService is the main interface for loading user data and is used by DaoAuthenticationProvider .
• UserDetailsService has a sub-interface, defines CRUD operations for user abstraction: UserDetailsManager
• JdbcDaoImpl is a JDBC implementation of UserDetailsService .
• JdbcUserDetailsManager is a JDBC implementation of UserDetailsManager and a JdbcDaoImpl extension. It also provides a GroupManager interface GroupManager

Based on differences, this can affect how you decide what to use, expose, wrap, or even implement.