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.

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

remove SecurityManager references #132

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

gurunrao
Copy link

remove SecurityManager references as per JEP 486 [ link - https://openjdk.org/jeps/486 ].

Important points captured from JEP 486 [ https://openjdk.org/jeps/486 ] for JDK24 + Security manager codes:

—------------------------------------------------------------------------------------------------------------------------------------------------------
In JDK 24, where a Security Manager is never enabled, the System::getSecurityManager and AccessController::doPrivileged methods behave as they did in JDK 17 when a Security Manager was not enabled,

System::getSecurityManager returns null,
The SecurityManager::check* methods throw SecurityException, and
The six AccessController::doPrivileged methods execute the given action immediately.

Rendering the Security Manager API non-functional

The Security Manager API consists of:

Methods in the java.lang.SecurityManager class,
Methods in the AccessController, AccessControlContext, Policy, and ProtectionDomain classes of the java.security package, and
The getSecurityManager and setSecurityManager methods in the java.lang.System class.

We are not removing these methods from Java 24; rather, we are changing them to have no effect. They will, as appropriate, return null or false, or pass through the caller's request, or unconditionally throw a SecurityException.

—---------------------------------------------------------------------------------------------------------------------------

@gurunrao gurunrao requested a review from a team as a code owner December 10, 2024 09:26
Copy link

Thank you for your pull request and welcome to our community! To contribute, please sign the Oracle Contributor Agreement (OCA).
The following contributors of this PR have not signed the OCA:

  • PR author: gurunrao

To sign the OCA, please create an Oracle account and sign the OCA in Oracle's Contributor Agreement Application.

When signing the OCA, please provide your GitHub username. After signing the OCA and getting an OCA approval from Oracle, this PR will be automatically updated.

If you are an Oracle employee, please make sure that you are a member of the main Oracle GitHub organization, and your membership in this organization is public.

@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Required At least one contributor does not have an approved Oracle Contributor Agreement. label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCA Required At least one contributor does not have an approved Oracle Contributor Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant