2.5. Data Security for Library Mode 2.5.1. Subject and Principal Classes To authorize access to resources, applications must first authenticate the request's source. The JAAS framework defines the term subject to represent a request's source. The Subject class is the central class in JAAS. A Subject represents information for a single entity, such as a person or service. It encompasses the entity's principals, public credentials, and private credentials. The JAAS APIs use the existing Java 2 java.security.Principal interface to represent a principal, which is a typed name. During the authentication process, a subject is populated with associated identities, or principals. A subject may have many principals. For example, a person may have a name principal (John Doe), a social security number principal (123-45-6789), and a user name principal (johnd), all of which help distinguish the subject from other subjects. To retrieve the principals associated with a subject, two methods are available: getPrincipals() returns all principals contained in the subject. getPrincipals(Class c) returns only those principals that are instances of class c or one of its subclasses. An empty set is returned if the subject has no matching principals. Note The java.security.acl.Group interface is a sub-interface of java.security.Principal , so an instance in the principals set may represent a logical grouping of other principals or groups of principals. Report a bug 2.5.2. Obtaining a Subject In order to use a secured cache in Library mode, you must obtain a javax.security.auth.Subject . The Subject represents information for a single cache entity, such as a person or a service. Red Hat JBoss Data Grid allows a JAAS Subject to be obtained either by using your container's features, or by using a third-party library. In JBoss containers, this can be done using the following: The Subject must be populated with a set of Principals, which represent the user and groups it belongs to in your security domain, for example, an LDAP or Active Directory. The Java EE API allows retrieval of a container-set Principal through the following methods: Servlets: ServletRequest.getUserPrincipal() EJBs: EJBContext.getCallerPrincipal() MessageDrivenBeans: MessageDrivenContext.getCallerPrincipal() The mapper is then used to identify the principals associated with the Subject and convert them into roles that correspond to those you have defined at the container level. A Principal is only one of the components of a Subject, which is retrieved from the java.security.AccessControlContext . Either the container sets the Subject on the AccessControlContext , or the user must map the Principal to an appropriate Subject before wrapping the call to the JBoss Data Grid API using a Security.doAs() method. Once a Subject has been obtained, the cache can be interacted with in the context of a PrivilegedAction. Example 2.7. Obtaining a Subject The Security.doAs() method is in place of the typical Subject.doAs() method. Unless the AccessControlContext must be modified for reasons specific to your application's security model, using Security.doAs() provides a performance advantage. To obtain the current Subject, use Security.getSubject(); , which will retrieve the Subject from either the JBoss Data Grid context, or from the AccessControlContext . Report a bug 2.5.3. Subject Authentication Subject Authentication requires a JAAS login. The login process consists of the following points: An application instantiates a LoginContext and passes in the name of the login configuration and a CallbackHandler to populate the Callback objects, as required by the configuration LoginModule s. The LoginContext consults a Configuration to load all the LoginModules included in the named login configuration. If no such named configuration exists the other configuration is used as a default. The application invokes the LoginContext.login method. The login method invokes all the loaded LoginModule s. As each LoginModule attempts to authenticate the subject, it invokes the handle method on the associated CallbackHandler to obtain the information required for the authentication process. The required information is passed to the handle method in the form of an array of Callback objects. Upon success, the LoginModule s associate relevant principals and credentials with the subject. The LoginContext returns the authentication status to the application. Success is represented by a return from the login method. Failure is represented through a LoginException being thrown by the login method. If authentication succeeds, the application retrieves the authenticated subject using the LoginContext.getSubject method. After the scope of the subject authentication is complete, all principals and related information associated with the subject by the login method can be removed by invoking the LoginContext.logout method. The LoginContext class provides the basic methods for authenticating subjects and offers a way to develop an application that is independent of the underlying authentication technology. The LoginContext consults a Configuration to determine the authentication services configured for a particular application. LoginModule classes represent the authentication services. Therefore, you can plug different login modules into an application without changing the application itself. The following code shows the steps required by an application to authenticate a subject. Developers integrate with an authentication technology by creating an implementation of the LoginModule interface. This allows an administrator to plug different authentication technologies into an application. You can chain together multiple LoginModule s to allow for more than one authentication technology to participate in the authentication process. For example, one LoginModule may perform user name/password-based authentication, while another may interface to hardware devices such as smart card readers or biometric authenticators. The life cycle of a LoginModule is driven by the LoginContext object against which the client creates and issues the login method. The process consists of two phases. The steps of the process are as follows: The LoginContext creates each configured LoginModule using its public no-arg constructor. Each LoginModule is initialized with a call to its initialize method. The Subject argument is guaranteed to be non-null. The signature of the initialize method is: public void initialize(Subject subject, CallbackHandler callbackHandler, Map sharedState, Map options) The login method is called to start the authentication process. For example, a method implementation might prompt the user for a user name and password and then verify the information against data stored in a naming service such as NIS or LDAP. Alternative implementations might interface to smart cards and biometric devices, or simply extract user information from the underlying operating system. The validation of user identity by each LoginModule is considered phase 1 of JAAS authentication. The signature of the login method is boolean login() throws LoginException . A LoginException indicates failure. A return value of true indicates that the method succeeded, whereas a return value of false indicates that the login module should be ignored. If the LoginContext 's overall authentication succeeds, commit is invoked on each LoginModule . If phase 1 succeeds for a LoginModule , then the commit method continues with phase 2 and associates the relevant principals, public credentials, and/or private credentials with the subject. If phase 1 fails for a LoginModule , then commit removes any previously stored authentication state, such as user names or passwords. The signature of the commit method is: boolean commit() throws LoginException . Failure to complete the commit phase is indicated by throwing a LoginException . A return of true indicates that the method succeeded, whereas a return of false indicates that the login module should be ignored. If the LoginContext 's overall authentication fails, then the abort method is invoked on each LoginModule . The abort method removes or destroys any authentication state created by the login or initialize methods. The signature of the abort method is boolean abort() throws LoginException . Failure to complete the abort phase is indicated by throwing a LoginException . A return of true indicates that the method succeeded, whereas a return of false indicates that the login module should be ignored. To remove the authentication state after a successful login, the application invokes logout on the LoginContext . This in turn results in a logout method invocation on each LoginModule . The logout method removes the principals and credentials originally associated with the subject during the commit operation. Credentials should be destroyed upon removal. The signature of the logout method is: boolean logout() throws LoginException . Failure to complete the logout process is indicated by throwing a LoginException . A return of true indicates that the method succeeded, whereas a return of false indicates that the login module should be ignored. When a LoginModule must communicate with the user to obtain authentication information, it uses a CallbackHandler object. Applications implement the CallbackHandler interface and pass it to the LoginContext , which send the authentication information directly to the underlying login modules. Login modules use the CallbackHandler both to gather input from users, such as a password or smart card PIN, and to supply information to users, such as status information. By allowing the application to specify the CallbackHandler , underlying LoginModule s remain independent from the different ways applications interact with users. For example, a CallbackHandler 's implementation for a GUI application might display a window to solicit user input. On the other hand, a CallbackHandler implementation for a non-GUI environment, such as an application server, might simply obtain credential information by using an application server API. The CallbackHandler interface has one method to implement: The Callback interface is the last authentication class we will look at. This is a tagging interface for which several default implementations are provided, including the NameCallback and PasswordCallback used in an earlier example. A LoginModule uses a Callback to request information required by the authentication mechanism. LoginModule s pass an array of Callback s directly to the CallbackHandler.handle method during the authentication's login phase. If a callbackhandler does not understand how to use a Callback object passed into the handle method, it throws an UnsupportedCallbackException to abort the login call. Report a bug 2.5.4. Authorization Using a SecurityManager In Red Hat JBoss Data Grid's Remote Client-Server mode, authorization is able to work without a SecurityManager for basic cache operations. In Library mode, a SecurityManager may also be used to perform some of the more complex tasks, such as distexec, map/reduce, and query. In order to enforce access restrictions, enable the SecurityManager in your JVM using one of the following methods: Command Line Programmaticaly Using the JDK's default implementation is not required, however an appropriate policy file must be supplied. The JBoss Data Grid distribution includes an example policy file, which demonstrates the permissions required by some of JBoss Data Grid's JAR files. These permissions must be integrated with those required by your application. Report a bug 2.5.5. Security Manager in Java 2.5.5.1. About the Java Security Manager Java Security Manager The Java Security Manager is a class that manages the external boundary of the Java Virtual Machine (JVM) sandbox, controlling how code executing within the JVM can interact with resources outside the JVM. When the Java Security Manager is activated, the Java API checks with the security manager for approval before executing a wide range of potentially unsafe operations. The Java Security Manager uses a security policy to determine whether a given action will be permitted or denied. Report a bug 2.5.5.2. About Java Security Manager Policies Security Policy A set of defined permissions for different classes of code. The Java Security Manager compares actions requested by applications against the security policy. If an action is allowed by the policy, the Security Manager will permit that action to take place. If the action is not allowed by the policy, the Security Manager will deny that action. The security policy can define permissions based on the location of code, on the code's signature, or based on the subject's principals. The Java Security Manager and the security policy used are configured using the Java Virtual Machine options java.security.manager and java.security.policy . Basic Information A security policy's entry consists of the following configuration elements, which are connected to the policytool : CodeBase The URL location (excluding the host and domain information) where the code originates from. This parameter is optional. SignedBy The alias used in the keystore to reference the signer whose private key was used to sign the code. This can be a single value or a comma-separated list of values. This parameter is optional. If omitted, presence or lack of a signature has no impact on the Java Security Manager. Principals A list of principal_type / principal_name pairs, which must be present within the executing thread's principal set. The Principals entry is optional. If it is omitted, it signifies that the principals of the executing thread will have no impact on the Java Security Manager. Permissions A permission is the access which is granted to the code. Many permissions are provided as part of the Java Enterprise Edition 6 (Java EE 6) specification. This document only covers additional permissions which are provided by JBoss EAP 6. Important Refer to your container documentation on how to configure the security policy, as it may differ depending on the implementation. 23152%2C+Security+Guide-6.608-09-2016+09%3A25%3A50JBoss+Data+Grid+6Documentation6.6.1 Report a bug 2.5.5.3. Write a Java Security Manager Policy Introduction An application called policytool is included with most JDK and JRE distributions, for the purpose of creating and editing Java Security Manager security policies. Detailed information about policytool is linked from http://docs.oracle.com/javase/6/docs/technotes/tools/ . Procedure 2.1. Setup a new Java Security Manager Policy Start policytool . Start the policytool tool in one of the following ways. Red Hat Enterprise Linux From your GUI or a command prompt, run /usr/bin/policytool . Microsoft Windows Server Run policytool.exe from your Start menu or from the bin\ of your Java installation. The location can vary. Create a policy. To create a policy, select Add Policy Entry . Add the parameters you need, then click Done . Edit an existing policy Select the policy from the list of existing policies, and select the Edit Policy Entry button. Edit the parameters as needed. Delete an existing policy. Select the policy from the list of existing policies, and select the Remove Policy Entry button. 23152%2C+Security+Guide-6.608-09-2016+09%3A25%3A50JBoss+Data+Grid+6Documentation6.6.1 Report a bug 2.5.5.4. Run Red Hat JBoss Data Grid Server Within the Java Security Manager To specify a Java Security Manager policy, you need to edit the Java options passed to the server instance during the bootstrap process. For this reason, you cannot pass the parameters as options to the standalone.sh script. The following procedure guides you through the steps of configuring your instance to run within a Java Security Manager policy. Prerequisites Before you following this procedure, you need to write a security policy, using the policytool command which is included with your Java Development Kit (JDK). This procedure assumes that your policy is located at JDG_HOME /bin/server.policy . As an alternative, write the security policy using any text editor and manually save it as JDG_HOME /bin/server.policy The JBoss Data Grid server must be completely stopped before you edit any configuration files. Perform the following procedure for each physical host or instance in your environment. Procedure 2.2. Configure the Security Manager for JBoss Data Grid Server Open the configuration file. Open the configuration file for editing. This location of this file is listed below by OS. Note that this is not the executable file used to start the server, but a configuration file that contains runtime parameters. For Linux: JDG_HOME /bin/standalone.conf For Windows: JDG_HOME \bin\standalone.conf.bat Add the Java options to the file. To ensure the Java options are used, add them to the code block that begins with: You can modify the -Djava.security.policy value to specify the exact location of your security policy. It should go onto one line only, with no line break. Using == when setting the -Djava.security.policy property specifies that the security manager will use only the specified policy file. Using = specifies that the security manager will use the specified policy combined with the policy set in the policy.url section of JAVA_HOME /lib/security/java.security . Important JBoss Enterprise Application Platform releases from 6.2.2 onwards require that the system property jboss.modules.policy-permissions is set to true . Example 2.8. standalone.conf Example 2.9. standalone.conf.bat Start the server. Start the server as normal. 23152%2C+Security+Guide-6.608-09-2016+09%3A25%3A50JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
public Set getPrincipals() {...} public Set getPrincipals(Class c) {...}
Subject subject = SecurityContextAssociation.getSubject();
import org.infinispan.security.Security; Security.doAs(subject, new PrivilegedExceptionAction<Void>() { public Void run() throws Exception { cache.put("key", "value"); } });
CallbackHandler handler = new MyHandler(); LoginContext lc = new LoginContext("some-config", handler); try { lc.login(); Subject subject = lc.getSubject(); } catch(LoginException e) { System.out.println("authentication failed"); e.printStackTrace(); } // Perform work as authenticated Subject // // Scope of work complete, logout to remove authentication info try { lc.logout(); } catch(LoginException e) { System.out.println("logout failed"); e.printStackTrace(); } // A sample MyHandler class class MyHandler implements CallbackHandler { public void handle(Callback[] callbacks) throws IOException, UnsupportedCallbackException { for (int i = 0; i < callbacks.length; i++) { if (callbacks[i] instanceof NameCallback) { NameCallback nc = (NameCallback)callbacks[i]; nc.setName(username); } else if (callbacks[i] instanceof PasswordCallback) { PasswordCallback pc = (PasswordCallback)callbacks[i]; pc.setPassword(password); } else { throw new UnsupportedCallbackException(callbacks[i], "Unrecognized Callback"); } } } }
void handle(Callback[] callbacks) throws java.io.IOException, UnsupportedCallbackException;
java -Djava.security.manager
System.setSecurityManager(new SecurityManager());
if [ "xUSDJAVA_OPTS" = "x" ]; then
JAVA_OPTS="USDJAVA_OPTS -Djava.security.manager -Djava.security.policy==USDPWD/server.policy -Djboss.home.dir=USDJBOSS_HOME -Djboss.modules.policy-permissions=true"
set "JAVA_OPTS=%JAVA_OPTS% -Djava.security.manager -Djava.security.policy==\path\to\server.policy -Djboss.home.dir=%JBOSS_HOME% -Djboss.modules.policy-permissions=true"