Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

6.5. Java Security Policy Statements

A policy file specifies permissions to modules and deployed applications. Permissions are applied to deployed applications via the VFS protocol. See the following Oracle Java SE documentation page Default Policy Implementation and Policy File Syntax for further information at http://docs.oracle.com/javase/7/docs/technotes/guides/security/PolicyFiles.html
The following is an example of policy statements. 
// Grant all to the jboss-modules.jar
grant codeBase "file:${jboss.home.dir}/jboss-modules.jar" {
  permission java.security.AllPermission;
};

// Standard extensions get all permissions by default
grant codeBase "file:${{java.ext.dirs}}/*" {
	permission java.security.AllPermission;
};

// Grant read PropertyPermission for all properties to a deployed EJB application
grant codeBase "vfs:/content/ejb-app.jar" {
  permission java.util.PropertyPermission "*", "read";
};

// Grant read FilePermission for all files to a web application
grant codeBase "vfs:/content/myapp.war/-" {
  permission java.io.FilePermission "/-", "read";
};
Copy to Clipboard Toggle word wrap

Note

On Microsoft Windows Server, when specifying a FilePermission statement including a file path in a string, not a codeBase URL, you must replace single backslash characters with two backslash characters. This is because when file paths are parsed, a single backslash is interpreted as an escape character.

Note

Two VFS issues currently exist in JBoss EAP that require a workaround:
  • If you define a grant for a deployment on Microsoft Windows, instead of: 
    grant codeBase "vfs:/content/..." {
    Copy to Clipboard Toggle word wrap
    you must use: 
    grant codeBase "vfs:/${user.dir}/content/..." {
    Copy to Clipboard Toggle word wrap
  • If your application contains JSPs, then the permissions granted to the deployment using a VFS URL is not sufficient, and you will have to duplicate it with file-based URL. For example, if you have permission: 
    grant codeBase "vfs:/content/application.war/-" {
  permission java.util.PropertyPermission "*", "read";
};
    Copy to Clipboard Toggle word wrap
    then you also need to add the following: 
    grant codeBase "file:${jboss.home.dir}/standalone/tmp/work/jboss.web/default-host/application/-" {
  permission java.util.PropertyPermission "*", "read";
};
    Copy to Clipboard Toggle word wrap
Module permissions are defined in module.xml (version 1.2 or higher). The following example demonstrates specifying module permissions. 
<module xmlns="urn:jboss:module:1.2" name="org.jboss.custom.module">
 <permissions>
  <grant permission="java.io.FilePermission" name="/-" actions="read"/>
  <grant permission="java.lang.RuntimePermission" name="org.jboss.*"/>
 </permissions>

 <resources>
  <resource-root path="custom-module.jar" />
 </resources>
</module>
Copy to Clipboard Toggle word wrap
If there is no <permissions/> element, then AllPermission permission is granted to the module. If there is an empty <permissions/> element, then no permission is granted.
Report a bug
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat