-
Notifications
You must be signed in to change notification settings - Fork 358
[FEATURE] Additional investigation why OpenSAML 4.3.0 wants to use intenal OpenSearch permission #2989
Description
Is your feature request related to a problem?
After switching to OpenSAML version 4.3.0. We found out that 2 additional properties need to be added to the security plugin policy file (the problem was fixed here #2987).
permission java.util.PropertyPermission "*" "read,write"; - is not a big deal since it just asks for access to the internal OpenSAML classes and JDK java.lang.ref.Cleaner
while
permission org.opensearch.secure_sm.ThreadPermission "modifyArbitraryThread - is the internal OpenSearch permission and technically we can't use it. Instead permission java.lang.RuntimePermission "modifyThread"; must be used.
What solution would you like?
To move forward with OpenSAML 4.3.0 we need investigate why it uses
permission org.opensearch.secure_sm.ThreadPermission "modifyArbitraryThread.
Do you have any additional context?
Add any other context or screenshots about the feature request here.