-
Notifications
You must be signed in to change notification settings - Fork 181
Spring Lemon Reactive Guide
Just like spring-lemon-jpa, spring-lemon-reactive is another leafs in the spring-lemon set of libraries, which your reactive monoliths or authentication services can use. It adds authentication functionalities to spring-lemon-commons-mongo. It comes with a lot of things, which are discussed below. To know how use these, please refer to the (demo reactive application)[https://github.com/naturalprogrammer/spring-lemon/tree/master/lemon-demo-reactive].
AbstractMongoUser comes with the essential user fields, such as email and password. Your User entity should inherit this. To know how, refer to the [demo reactive application|https://github.com/naturalprogrammer/spring-lemon/tree/master/lemon-demo-reactive].
The roles field of AbstractUser holds all the user roles. It's a set of String, and so you're free to add any custom roles you may want to use in your application.
LemonReactiveSecurityConfig, along with all the helper beans in the com.naturalprogrammer.spring.lemonreactive.security package, are responsible for configuring security of your application.
It's quite customizable — provide your own bean to override a built-in one.
UniqueEmail and UniqueEmailValidator define a constraint that's used in AbstractMongoUser for ensuring uniqueness of emails of the user.
LemonReactiveController and LemonReactiveService classes define a user-module API. You'll need to extend these. To know how, refer to the [demo reactive application|https://github.com/naturalprogrammer/spring-lemon/tree/master/lemon-demo-reactive].
LemonReactiveService is composed of many protected methods, which could be overridden for any customization.
LerUtils contains a few of utility methods.