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

[Security Manager Replacement] Add support of Java policies #17663

Merged
merged 2 commits into from
Mar 25, 2025

Conversation

reta
Copy link
Collaborator

@reta reta commented Mar 24, 2025

Description

As of JDK-24, the use of Java policies has been restricted. However, in order for OpenSearch to continue working post JDK-24, we should provide the support of Java policies.

Related Issues

Closes #17659

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Copy link
Contributor

❌ Gradle check result for dc87ede: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@kumargu
Copy link
Contributor

kumargu commented Mar 24, 2025

@andrross @kumargu @cwperks very much aware that there are no tests (yet) added into to these modules yet, severe lack of time, but I have ported these files from the JDK codebase mostly as-is.

I think its fine to not have unit tests for the (large) ported files, our integration test would cover parts of it. Also. I think these files would be barely changed.

@kumargu
Copy link
Contributor

kumargu commented Mar 24, 2025

overall LGTM.

@cwperks
Copy link
Member

cwperks commented Mar 24, 2025

@andrross @kumargu @cwperks very much aware that there are no tests (yet) added into to these modules yet, severe lack of time, but I have ported these files from the JDK codebase mostly as-is.

I think its fine to not have unit tests for the (large) ported files, our integration test would cover parts of it. Also. I think these files would be barely changed.

Agree here for the sake of this PR. The logic in the files will be covered by ITs that read the policy files even if the individual units do not have tests. It would be a good idea to add tests, but I would be comfortable with that done in a separate future PR.

Signed-off-by: Andriy Redko <andriy.redko@aiven.io>
@github-actions github-actions bot added the security Anything security related label Mar 24, 2025
Copy link
Contributor

❌ Gradle check result for cdf3a2e: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

❌ Gradle check result for cdf3a2e: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

❌ Gradle check result for cdf3a2e: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

❌ Gradle check result for cdf3a2e: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

❌ Gradle check result for cdf3a2e: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

✅ Gradle check result for cdf3a2e: SUCCESS

@reta
Copy link
Collaborator Author

reta commented Mar 25, 2025

@cwperks mind please re-approving, conflicts :-(, thank you

@cwperks
Copy link
Member

cwperks commented Mar 25, 2025

@cwperks mind please re-approving, conflicts :-(, thank you

approved

@andrross andrross merged commit 17289b7 into opensearch-project:main Mar 25, 2025
31 of 32 checks passed
andrross added a commit to andrross/OpenSearch that referenced this pull request Mar 26, 2025
andrross added a commit to andrross/OpenSearch that referenced this pull request Mar 26, 2025
This reverts commit 17289b7.

Signed-off-by: Andrew Ross <andrross@amazon.com>
andrross added a commit to andrross/OpenSearch that referenced this pull request Mar 27, 2025
This reverts commit 17289b7.

Signed-off-by: Andrew Ross <andrross@amazon.com>
reta pushed a commit that referenced this pull request Mar 28, 2025
* Revert "Add simple PolicyParser unit test (#17690)"

This reverts commit 3fb09c7.

Signed-off-by: Andrew Ross <andrross@amazon.com>

* Revert "Add support of Java policies (#17663)"

This reverts commit 17289b7.

Signed-off-by: Andrew Ross <andrross@amazon.com>

---------

Signed-off-by: Andrew Ross <andrross@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement or improvement to existing feature or request _No response_ security Anything security related v3.0.0 Issues and PRs related to version 3.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature Request] Add support of Java policies
5 participants