Configure Java 2 security



  1. Verify that required permissions for the APIs used are declared was.policy.

  2. Verify that migrated applications from previous releases are given the required permissions. Since Java 2 security is not supported or partially supported in previous WAS releases, applications developed prior to Version 5 most likely are not using the Java 2 security programming model. There is no easy way to find out all the required permissions for the application. Following are activities you can perform to determine the extra permissions required by an application...

    • Code review and code inspection

    • Application documentation review

    • Sandbox testing of migrated enterprise applications with Java 2 security enabled in a pre-production environment. Enable tracing in WebSphere Java 2 security manager to help determine the missing permissions in the application policy file. The trace specification is...

    • Use the system property to aid debuggging. This property should not be used in a production environment. Refer to Java 2 security.

The default permission set for applications is the recommended permission set defined in the J2EE 1.3 Specification. The default is declared in...


...policy file with permissions defined in the Development Kit...


...policy file that grant permissions to everyone. However, applications are denied permissions declared in...


Permissions declared in the filter.policy file are filtered for applications during the permission check.

Define the required permissions for an application in a was.policy file and embed the was.policy file in the EAR file as...



Turn on Java 2 security

  1. Click through: "Security | Global Security"

  2. Enable Java 2 security by selecting the check box labeled Enforce Java 2 Security (clear the check box for disabling Java 2 Security).

  3. Click OK or Apply, and then Save

  4. Restart the server for the changes to take effect.

Java 2 security is enabled and enforced for the servers. Java 2 security permission is selected when a Java 2 security protected API is called.


When to use Java 2 security.

  1. To enable protection on system resources. For example, when opening or listening to a socket connection, reading or writing to operating system file systems, reading or writing Java Virtual Machine system properties, and so on.

  2. To prevent application code calling destructive APIs. For example, calling the System.exit() method brings down the appserver.

  3. To prevent application code from obtaining privileged information (passwords) or gaining extra privileges (obtaining server credentials).

The WebSphere Java 2 security manager can dump the Java 2 security permissions granted to all classes on the call stack when an application is denied access to a resource. To enable this feature, set the server trace service using...

When the exception is thrown, the dump provides hints to determine whether the application is missing permissions or the product run time code or third party libraries used are not properly marked as privileged when accessing Java 2 protected resources.