Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Jakarta Authorization 2.1 Plan Review #361

Merged
merged 3 commits into from Jun 9, 2021
Merged

Jakarta Authorization 2.1 Plan Review #361

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
85a0938
Jakarta Authorization 3.0 Plan Review
arjantijms Apr 14, 2021
aa0ecfd
Update _index.md
arjantijms May 19, 2021
0d56c84
Rename authorization/3.0/_index.md to authorization/2.1/_index.md
arjantijms May 19, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
44 changes: 44 additions & 0 deletions authorization/2.1/_index.md
View file
Open in desktop
@@ -0,0 +1,44 @@
---
title: "Jakarta Authorization 2.1 (under development)"
date: 2021-05-19
summary: "Release for Jakarta EE 10"
---
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 primary goal of this release is to make Jakarta Authorization more suitable for cloud deployments, by adding an option to add policy providers programmatically for a single application. This mirrors the API available for Jakarta Authentication.

More specifically:

* Register a policy provider programmatically per application [AUTHORIZATION #98](https://github.com/eclipse-ee4j/authorization/issues/98)
* getPolicyConfiguration without open requirement [AUTHORIZATION #53](https://github.com/eclipse-ee4j/authorization/issues/53)
* Add methods to the PolicyConfiguration to read permissions [AUTHORIZATION #52](https://github.com/eclipse-ee4j/authorization/issues/52)

The JDK version required will be aligned with Jakarta EE 10.

* [Jakarta Authorization 2.1 Release Record](https://projects.eclipse.org/projects/ee4j.jacc/releases/2.1)

# Ballots

## Plan Review
<!--
The Specification Committee Ballot concluded successfully on 2021-xx-xx with the following results.

| Representative | Representative for: | Vote |
|------------------------------------------------|---------------------|------|
| Kenji Kazumura | Fujitsu | |
| Dan Bandera, Kevin Sutter | IBM | |
| Ed Bratt, Dmitry Kornilov | Oracle | |
| Andrew Pielage, Matt Gill | Payara | |
| Scott Stark, Mark Little | Red Hat | |
| David Blevins, Jean-Louis Monteiro | Tomitribe | |
| Ivar Grimstad | EE4J PMC | |
| Marcelo Ancelmo, Martijn Verburg | Participant Members | |
| Werner Keil | Committer Members | |
| Scott (Congquan) Wang | Enterprise Members | |
| | Total | |

The ballot was run in the [jakarta.ee-spec mailing list]()
-->