Matthew T. Adams (Migrated from SEC-1737) said:

Sometimes it's handy to have a JPA-based UserDetailsService or UserDetailsManager instead of a JDBC-based one. The attached classes are abstract classes that do the boilerplate work of the UserDetailsService & UserDetailsManager implementation, defining abstract methods for subclasses to implement for the user's specific entities that represent users & groups.

Contributing since I considered it helpful, and I figured others might like to have it. It does introduce a dependency on JPA, so should probably go into some kind of separate contrib module outside of core.

Hope you likey.

Comment From: spring-projects-issues

Matthew T. Adams said:

Just noticed JpaUserDetailsManager.java should probably be in the package org.springframework.security.provisioning to align with JdbcUserDetailsManager.

Comment From: rwinch

Thank you for the report. We are not going to provide additional implementations of UserDetaisService as it will get difficult to maintain. Additionally, we are unlikely to provide all the attributes users want, so they will likely need to provide their own. Finally, it is easy enough for user's to provide their own implementation. For these reasons, I'm closing this as declined.