JDK-8177415 : Release Note: Custom Policy Providers may need additional configuration
- Type: Sub-task
- Component: security-libs
- Sub-Component: java.security
- Affected Version: 9
- Priority: P2
- Status: Closed
- Resolution: Delivered
- Submitted: 2017-03-22
- Updated: 2017-09-22
- Resolved: 2017-03-22
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 9 |
|---|
9Resolved  |
Description
Classes loaded from the extensions directory are no longer granted `AllPermission` by default. See JDK-8040059. A custom `java.security.Policy` provider that was using the extensions mechanism may be depending on the policy grant statement that had previously granted it `AllPermission`. If the policy provider does anything that requires a permission check, the local policy file may need to be adjusted to grant those permissions. Also, custom policy providers are loaded by the system class loader. The `classpath` may need to be configured to allow the provider to be located.