JDK-8268349 : Provide clear run-time warnings about Security Manager deprecation
- Type: Bug
- Component: security-libs
- Sub-Component: java.security
- Affected Version: 17
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2021-06-07
- Updated: 2022-01-31
- Resolved: 2021-06-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 17 | JDK 18 |
|---|---|
17 b28Fixed  |
18Fixed |
Related Reports
|
CSR :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
In connection with JEP 411, provide clear warnings when a Security Manager is enabled at startup or installed at run time. If a command line option prevents a Security Manager from being installed at run time, provide a clear message in the UnsupportedOperationException thrown by System::setSecurityManager. See the CSR for further details.
Comments
|