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
单击下面的规范以访问规范文档、Javadoc、技术兼容性工具包(TCK)以及每个版本的规范的兼容实现.
Jakarta EE Platform and Profile 规范是各个规范的总括规范。Jakarta EE Platform 包括大多数单独的规范，而 Profile 规范包括用于开发Web平台和微服务体系结构的单独规范.
每个单独的规范都描述了实现企业Java应用程序的特定方面的标准化方式.