Spring Security Custom User Detail Service: Difference between revisions
Jump to navigation
Jump to search
Line 6: | Line 6: | ||
This approach is useful for the situation in which the user information should be part of the application's domain model. | 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. | |||
=Playground Example= | =Playground Example= | ||
{{External|[https://github.com/ovidiuf/playground/tree/master/spring/spring-in-action/cap4-security-user-detail-service Playground - Spring Security - User Detail Service]}} | {{External|[https://github.com/ovidiuf/playground/tree/master/spring/spring-in-action/cap4-security-user-detail-service Playground - Spring Security - User Detail Service]}} |
Revision as of 20:02, 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.