Spring Security Custom User Detail Service: Difference between revisions
Jump to navigation
Jump to search
Line 13: | Line 13: | ||
public interface UserRepository extends CrudRepository<User, Long> { | public interface UserRepository extends CrudRepository<User, Long> { | ||
User findByUsername(String username); | User findByUsername(String username); | ||
} | |||
</syntaxhighlight> | |||
* Create a UserDetailsService interface: | |||
<syntaxhighlight lang='java'> | |||
public interface UserDetailsService { | |||
UserDetails loadUserByUsername(String username) throws UsernameNotFoundException; | |||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> |
Revision as of 20:21, 10 November 2018
Internal
Overview
This approach is useful for the situation in which the user information should be part of the application's domain model.
Combining application authentication and authorization with domain model user information largely consists in the following steps:
- Declare a User entity that should implement the Spring UserDetails interface. Implementation of UserDetails provides essential user information to the framework, in a standard fashion (whether the account is enabled or not, authorities, etc.). Implementing UserInterface on a generic user domain model entity is the programmatic way of modifying the generic user entity to make it useful for authentication.
- Declare the corresponding repository interface:
public interface UserRepository extends CrudRepository<User, Long> {
User findByUsername(String username);
}
- Create a UserDetailsService interface:
public interface UserDetailsService {
UserDetails loadUserByUsername(String username) throws UsernameNotFoundException;
}