Before you begin
Java 2 security uses several policy files to determine the granted permissions for each Java programs. See the Java 2 security policy files article for the list of available policy files supported by WebSphere Application Server.Policy file name | Description |
---|---|
app.policy | Contains default permissions for all of the enterprise applications in the cell. |
was.policy | Contains application-specific permissions for an WebSphere Application Server enterprise application. This file is packaged in an enterprise archive (EAR) file. |
ra.xml | Contains connector application specific permissions for a WebSphere Application Server enterprise application. This file is packaged in a resource adapter archive (RAR) file. |
spi.policy | Contains permissions for Service Provider Interface (SPI) or third-party resources embedded in WebSphere Application Server. The default contents grant everything. Update this file carefully when the cell requires more protection against SPI in the cell. This file is applied to all of the SPIs defined in the resources.xml file. |
library.policy | Contains permissions for the shared library of enterprise applications. |
filter.policy | Contains the list of permissions that require filtering from the was.policy file and the app.policy file in the cell. This filtering mechanism only applies to the was.policy and app.policy files. |
grant codeBase "file:${application}" {
permission java.lang.RuntimePermission "stopThread";
permission java.lang.RuntimePermission "modifyThread";
permission java.lang.RuntimePermission "modifyThreadGroup";
};
Steps for this task
Add any permission that should never be granted to the WebSphere Application Server enterprise application in the cell to the filter.policy file. Refer to Configuring filter.policy files.
Result
The required permission is granted for the specified WebSphere Application Server enterprise application.Example
java.security.AccessControlException: access denied (java.io.FilePermission
C:\WebSphere\AppServer\java\jre\lib\ext\mail.jar read)
The previous two lines were split onto two lines because of the width of the page. However, the permission should be on one line.
grant codeBase "file:<user client installed location>" {
permission java.io.FilePermission
"C:\WebSphere\AppServer\java\jre\lib\ext\mail.jar", "read";
};
The previous two lines were split onto two lines because of the width of the page. However, the permission should be on one line.
To decide whether to add a permission, refer to the article Access control exception.
Related concepts
Java 2 security policy files
Access control exception
Related tasks
Migrating security configurations from previous releases
Configuring static policy files
Related reference
Java 2 security