JDK-8193032 : Remove terminally deprecated SecurityManager APIs
- Type: Sub-task
- Component: security-libs
- Sub-Component: java.security
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2017-12-05
- Updated: 2018-04-16
- Resolved: 2018-04-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 11 |
|---|
11 b08Fixed  |
Related Reports
|
CSR :
|
|
|
Relates :
|
|
|
Relates :
|
Description
In JDK 1.8, the following methods of java.lang.SecurityManager were deprecated: boolean SecurityManager.checkTopLevelWindow(java.lang.Object) void SecurityManager.checkSystemClipboardAccess() void SecurityManager.checkAwtEventQueueAccess() void SecurityManager.checkMemberAccess(java.lang.Class,int) In JDK 9, the methods were marked for removal as part of JDK-8145468. Also in JDK 9, the first three methods were changed to check AllPermission by JDK-8029886, and in JDK 10 checkMemberAccess was changed to check AllPermission by JDK-8186535. These methods should be removed from a subsequent JDK feature release, possibly JDK 11. (Other terminally deprecated SecurityManager APIs that had been deprecated since JDK 1.2 were removed from JDK 10. See JDK-8186535.)