JSR 392 (Java SE 17): JEP Proposed to Target: 411: Deprecate the Security Manager for Removal

Iris Clark iris.clark at oracle.com
Sat May 22 01:26:07 UTC 2021

The following JEP with scope "SE" has been proposed to target JDK 17:

  411: Deprecate the Security Manager for Removal

  Summary: Deprecate the Security Manager for removal in a future
  release. The Security Manager dates from Java 1.0. It has not been the
  primary means of securing client-side Java code for many years, and it
  has rarely been used to secure server-side code. To move Java forward,
  we intend to deprecate the Security Manager for removal in concert with
  the legacy Applet API (JEP 398).

The announced deadline for feedback to jdk-dev is Fri 28 May 23:59 UTC:


If there are no unresolved objections at that time, then the JEP will be moved
to the Targeted state, indicating that the feature is expected to appear in
the specified release of the JDK Project.  For more information about states,
see the JEP Process document:


A dashboard that lists JEPs with "SE" scope may be found via a link on this



More information about the java-se-spec-experts mailing list