Notice: Some of the services that support the smooth operation of our websites are still in the process of being restored. As a result, certain features—such as images and committer paperwork—may be temporarily unavailable. Our team is actively working to resolve these issues and restore full functionality as soon as possible.

Thank you for your patience and understanding.

Jakarta Security 4.0 Release Review

Type
Release
State
Successful
End Date of the Review Period

Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.

Project
Jakarta Security
Release

4.0

Description

The goal of this release is to continue adding features and evolving the API.

More specifically:

  • Basic API (handler) for Multiple authentication mechanisms
  • Qualifiers for build-in authentication mechanisms
  • In-memory identity store

 

Removals, deprecations or backwards incompatible changes

  • Remove references to the SecurityManager (as listed here: https://github.com/search?q=repo%3Ajakartaee%2Fsecurity%20SecurityManager&type=code)
  • Build-in authentication mechanisms now have a qualifier by default, whereas before they were unqualified

(Note, Jakarta Security does not use the SecurityManager explicitly, but it shows up as a somewhat internal detail in the API code)

 

 

Conforms To UI/UX Guidelines
Not verified
Links
GitHub PR