Chapter 16. Java Authorization Contract for Containers (JACC)
16.1. About Java Authorization Contract for Containers (JACC)
Java Authorization Contract for Containers (JACC) is a standard which defines a contract between containers and authorization service providers, which results in the implementation of providers for use by containers. It is defined in JSR-115 of the Java Community Process. For details about the specifications, see Java™ Authorization Contract for Containers.
JBoss EAP implements support for JACC within the security functionality of the
16.2. Configure Java Authorization Contract for Containers (JACC) Security
You can configure Java Authorization Contract for Containers (JACC) by configuring your security domain with the correct module, and then modifying your
jboss-web.xml to include the required parameters.
Add JACC Support to the Security Domain
To add JACC support to the security domain, add the
JACC authorization policy to the authorization stack of the security domain, with the
required flag set. The following is an example of a security domain with JACC support. However, it is recommended to configure the security domain from the management console or the management CLI, rather than directly modifying the XML.
Example: Security Domain with JACC Support
<security-domain name="jacc" cache-type="default"> <authentication> <login-module code="UsersRoles" flag="required"> </login-module> </authentication> <authorization> <policy-module code="JACC" flag="required"/> </authorization> </security-domain>
Configure a Web Application to Use JACC
jboss-web.xml file is located in the
WEB-INF/ directory of your deployment, and contains overrides and additional JBoss-specific configuration for the web container. To use your JACC-enabled security domain, you need to include the
<security-domain> element, and also set the
<use-jboss-authorization> element to
true. The following XML is configured to use the JACC security domain above.
Example: Utilize the JACC Security Domain
<jboss-web> <security-domain>jacc</security-domain> <use-jboss-authorization>true</use-jboss-authorization> </jboss-web>
Configure an EJB Application to Use JACC
Configuring EJBs to use a security domain and to use JACC differs from web applications. For an EJB, you can declare method permissions on a method or group of methods, in the
ejb-jar.xml descriptor. Within the
<ejb-jar> element, any child
<method-permission> elements contain information about JACC roles. See the example configuration below for details. The
EJBMethodPermission class is part of the Java EE 7 API, and is documented at http://docs.oracle.com/javaee/7/api/javax/security/jacc/EJBMethodPermission.html.
Example: JACC Method Permissions in an EJB
<ejb-jar> <assembly-descriptor> <method-permission> <description>The employee and temp-employee roles may access any method of the EmployeeService bean </description> <role-name>employee</role-name> <role-name>temp-employee</role-name> <method> <ejb-name>EmployeeService</ejb-name> <method-name>*</method-name> </method> </method-permission> </assembly-descriptor> </ejb-jar>
You can also constrain the authentication and authorization mechanisms for an EJB by using a security domain, just as you can do for a web application. Security domains are declared in the
jboss-ejb3.xml descriptor, in the
<security> child element. In addition to the security domain, you can also specify the
<run-as-principal>, which changes the principal that the EJB runs as.
Example: Security Domain Declaration in an EJB
<ejb-jar> <assembly-descriptor> <security> <ejb-name>*</ejb-name> <security-domain>myDomain</security-domain> <run-as-principal>myPrincipal</run-as-principal> </security> </assembly-descriptor> </ejb-jar>