WAS v8.5 > Develop applications > Develop security > Develop extensions to the WebSphere security infrastructure > Develop applications that use programmatic security

Protecting system resources and APIs (Java 2 security) for developing applications

Java 2 security is a programming model that is very pervasive and has a huge impact on application development.

Java 2 security is orthogonal to Java EE role-based security; we can disable or enable it independently of administrative security.

However, it does provide an extra level of access control protection on top of the Java EE role-based authorization. It particularly addresses the protection of system resources and application programming interfaces (API). Administrators need to consider the benefits against the risks of disabling Java 2 security.

The following recommendations are provided to help enable Java 2 security in a test or production environment:

  1. Verify the application is developed with the Java 2 security programming model. Developers have to know whether or not the APIs used in the applications are protected by Java 2 security. It is very important the required permissions for the APIs used are declared in the policy file (was.policy), or the application fails to run when Java 2 security is enabled. Developers can reference the website for Development Kit APIs that are protected by Java 2 security. See the Programming model and decisions section of the Security: Resources for Learning topic to visit this website.
  2. Make sure that migrated applications from previous releases are given the required permissions. Because Java 2 security is not supported or partially supported in previous WebSphere Application Server releases, applications developed prior to v5 most likely are not using the Java 2 security programming model. No easy way to find out all the required permissions for the application is available. The following are activities we 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 preproduction environment. Enable tracing in WebSphere Java 2 security manager to help determine the missing permissions in the application policy file. The trace specification is: com.ibm.ws.security.core.SecurityManager=all=enabled.

    • Use the com.ibm.websphere.java2secman.norethrow system property to aid debugging. Do not use this property 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 the app_server_root/profiles/profile_name/config/cells/cell_name/nodes/node_name/app.policy policy file with permissions defined in the Development Kit (JAVA_HOME/jre/lib/security/java.policy) policy file that grant permissions to everyone. However, applications are denied permissions that are declared in the profiles/profile_name/config/cells/cell_name/filter.policy file. Permissions that are 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 application EAR file as YOURAPP.ear/META-INF/was.policy, see Configure Java 2 security policy files for details.

The following steps describe how to enforce Java 2 security on the cell level for WAS, Network Deployment and the server level for WAS, Express

  1. Click Security > Global security. The Global security panel is displayed.

  2. Select the Use Java 2 security to restrict application access to local resources option.

  3. Click OK or Apply.

  4. Click Save to save the changes.

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


Results

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. 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. Prevent application code from calling destructive APIs, for example, calling the System.exit method brings down the application server.
  3. Prevent application code from obtaining privileged information (passwords) or gaining extra privileges (obtaining server credentials).

The Java 2 security manager is enhanced to dump the Java 2 security permissions that are granted to all classes on the call stack when an application is denied access to a resource. The java.security.AccessControlException exception is created. However, this tracing capability is disabled by default. We can enable this capability by specifying the server trace service with the com.ibm.ws.security.core.SecurityManager=all=enabled trace specification. When the exception is created, the trace dump provides hints to determine whether the application is missing permissions or the product runtime code or the third-party libraries used are not properly marked as privileged when accessing Java 2 security-protected resources.

See the Security Problem Determination Guide for details.


Subtopics


Related


Develop applications that use programmatic security
Migrating Java 2 security policy
Migrate, coexist, and interoperate – Security considerations


Reference:

Security: Resources for learning


+

Search Tips   |   Advanced Search