Jakarta Security 3.0 (under development)
Jakarta Security defines a standard for creating secure Jakarta EE applications in modern application paradigms.
The goal of this release is to continue adding features and evolving the API. A number of those had been discussed and even had prototype implementations during the development of the previous version, but didn’t make it in.
Additional authentication mechanisms:
Extended authentication mechanisms:
- Authentication mechanism per URL SECURIY #86
- User choice of authentication mechanism (login with provider X, login with provider Y, etc)
- Multiple authentication mechanisms (try JWT, fallback to BASIC, etc)
- @RolesAllowed alternative
- Easily adding an interceptor to a build-in CDI bean blog
- Authorization modules blog
The JDK version required will be aligned with Jakarta EE 10.
The Specification Committee Ballot concluded successfully on 2021-05-27 with the following results.
|Dan Bandera, Kevin Sutter
|Ed Bratt, Dmitry Kornilov
|Andrew Pielage, Matt Gill
|Scott Stark, Mark Little
|David Blevins, Jean-Louis Monteiro
|Marcelo Ancelmo, Martijn Verburg
|Scott (Congquan) Wang
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.
Platform and Profile Specifications
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.