JDK-8267184 : Add -Djava.security.manager=allow to tests calling System.setSecurityManager
- Type: Enhancement
- Component: security-libs
- Sub-Component: java.security
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2021-05-14
- Updated: 2022-06-08
- Resolved: 2021-05-24
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 17 |
|---|
17 b24Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
Any test calling System.setSecurityManager() would fail if the "java.security.manager" system property is "disallow". We should add "-Djava.security.manager=allow" to these tests.
Comments
|