activity-based-security-framework
avaje-validator
| activity-based-security-framework | avaje-validator | |
|---|---|---|
| 1 | 1 | |
| 19 | 26 | |
| - | - | |
| 0.0 | 9.3 | |
| over 1 year ago | 25 days ago | |
| Java | Java | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
activity-based-security-framework
-
Architectural approaches to authorization in server applications: Activity-Based Access Control Framework
Throughout my years working in the IT sphere, I’ve had the opportunity to work on projects in a variety of fields. Even though the process of authenticating requirements remained relatively consistent, methods of implementing the authorization mechanism tended to be quite different from project to project. Authorization had to be written practically from scratch for the specific goals of each project; we had to develop an architectural solution, then modify it with changing requirements, test it, etc. All this was considered a common process that developers could not avoid. Every time someone implemented a new architectural approach, we felt more and more that we should come up with a general approach that would cover the main authorization tasks and (most importantly) could be reused on other applications. This article takes a look at a generalized architectural approach to authorization based on an example of a developed framework.
avaje-validator
What are some alternatives?
sureness - A simple and efficient security framework that focus on protection of API.
shadow - annotation processor api
Spring Boot - Spring Boot
jbock - Reflectionless command line parser
Spring Security - Spring Security
java-fluent-validator - Java Fluent Validator is inspired by Fluent Interface and .Net FluentValidation which defined an inner-DSL within Java language for programmers to use. A fluent interface implies that its primary goal is to make it easy to SPEAK and UNDERSTAND.
avaje-inject - Dependency injection via APT (source code generation) ala "Server-Side Dagger DI"
yavi - Yet Another Validation for Java (A lambda based type safe validation framework)
Make-Java-Easy - A Library / Package that makes writing java as easy as Python!
1. AutoProxy - Annotation Processing Library. Generates proxy class on top of interface/abstract class, that allows to intercept calls. Also known as a design pattern: proxy, delegate, interceptor.