Jakarta Authentication defines a general low-level SPI for authentication mechanisms, which are controllers that interact with a caller and a container’s environment to obtain the caller’s credentials, validate these, and pass an authenticated identity (such as name and groups) to the container.
Jakarta Authentication consists of several profiles, with each profile telling how a specific container (such as Jakarta Servlet) can integrate with- and adapt to this SPI.
The Specification Committee Ballot concluded successfully on 2019-09-02 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.