JDK-8271742 : Release Note: JEP 411: Deprecate the Security Manager for Removal
- Type: Sub-task
- Component: security-libs
- Sub-Component: java.security
- Affected Version: 17
- Priority: P3
- Status: Resolved
- Resolution: Delivered
- Submitted: 2021-08-03
- Updated: 2021-08-16
- Resolved: 2021-08-04
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 |
|---|
17Resolved  |
Description
The Security Manager and APIs related to it have been deprecated and will be removed in a future release. To ensure that developers and users are aware that the Security Manager is deprecated for removal, the Java runtime issues a warning at startup if the Security Manager is enabled on the command line via `java -Djava.security.manager`. The Java runtime also issues a warning at run time if the Security Manager is enabled dynamically via the `System::setSecurityManager` API. These warnings cannot be disabled. See [JEP 411](https://openjdk.java.net/jeps/411) for more information and a list of APIs that have been deprecated for removal.