sureness | A simple and efficient security framework that focus on protection of API | Security Framework library

Resource path matching see: URI Match. When use maven or gradle build project, add coordinate. The default configuration -DefaultSurenessConfig uses the document datasource sureness.yml as the auth datasource. It supports JWT auth, Basic auth, Digest authentication. Sureness authentication requires us to provide our own account data, role permission data, etc. These data may come from text, relational databases, non-relational databases, annotations, etc. We provide interfaces SurenessAccountProvider, PathTreeProvider for user implement to load data from the dataSource where they want. Default Document DataSource Config - sureness.yml, see: Default Document DataSource Annotation DataSource Config Detail - AnnotationLoader, see: Annotation DataSource. If the configuration resource data comes from text, please refer to Sureness integration Spring Boot sample(configuration file scheme) If the configuration resource data comes from dataBase, please refer to Sureness integration Spring Boot sample(database scheme). The essence of Sureness is to intercept all rest requests for authenticating and authorizing. The interceptor can be a filter or a Spring interceptor, it intercepts all request to check them.
Based RBAC, User-Role-Resource.
We treat API requests as a resource, resource format like requestUri===httpMethod. That is the request uri + request method(post,get,put,delete...) is considered as a resource as a whole. eg: /api/v2/book===get
User belongs some Role -- Role owns Resource -- User can access the resource.
SurenessAccountProvider - Account datasource provider interface.
PathTreeProvider - Resource uri-role datasource provider interface.
If auth success, method - checkIn will return a SubjectSum object containing user information.
If auth failure, method - checkIn will throw different types of auth exceptions.