Jakarta Authorization defines a low-level SPI for authorization modules, which are repositories of permissions facilitating subject based security by determining whether a given subject has a given permission, and algorithms to transform security constraints for specific containers (such as Jakarta Servlet or Jakarta Enterprise Beans) into these permissions.
The Specification Committee Ballot concluded successfully on 2019-09-06 with the following results.
| Yes | No | Abstain | |
|---|---|---|---|
| Fujitsu | +1 | ||
| IBM | +1 | ||
| Oracle | +1 | ||
| Payara | +1 | ||
| Red Hat | +1 | ||
| Tomitribe | +1 | ||
| EE4J PMC | +1 | ||
| Participant Members | +1 | ||
| Committer Members | +1 |
The ballot was run in the jakarta.ee-spec mailing list
Click on the specifications below to access the specification document, Javadoc, Technology Compatibility Kit (TCK), and compatible implementation for each release of the specification.
The Jakarta EE Platform and Profile specifications are the umbrella specifications for the individual specifications. The Jakarta EE Platform includes most of the individual specifications, while the Profile specifications include the individual specifications for developing web platforms and microservices architectures.
Each individual specification describes a standardized way of implementing a particular aspect of an enterprise Java application.