Administration guide > Secure the deployment environment > Tutorial: Integrate WebSphere eXtreme Scale security with WAS > Module 2: Configure WebSphere eXtreme Scale to use WAS Authentication plug-ins
Secure the deployment environment > Tutorial: Integrate WebSphere eXtreme Scale security with WAS > Module 2: Configure WebSphere eXtreme Scale to use WAS Authentication plug-ins >
< Previous | Next >
Lesson 2.3: Configure container server security
When a container server connects to the catalog service, the container server gets all the security configurations that are configured in the Object Grid Security XML file, such as authenticator configuration, the login session timeout value, and other configuration information. A container server also has its own server-specific security properties in the server property file.
Configure the server property file with the -Dobjectgrid.server.props Java virtual machine (JVM) property. The file name for this property is an absolute file path, such as samples_home/security/server2.props.
In this tutorial, the container servers are hosted in the xs1 and xs2 servers in the xsCluster cluster.
Security integration with WAS
Start secure servers in WAS
Start and stop servers in a WAS environment
Security descriptor XML file
Server properties file
The server2.props file is in the samples_home/security directory under the WASSecurity directory. The properties that are defined in the server2.props file follow:
- The securityEnabled property is set to true to indicate that this container server is a secure server.
- The credentialAuthentication property is set to Required, so any client that is connecting to the server is required to provide a credential.
- The secureTokenManagerType is set to none to indicate that the authentication secret is not encrypted when joining the existing servers.
- The authenticationSecret property is set to ObjectGridDefaultSecret. This secret string is used to join the eXtreme Scale server cluster. When a server joins the data grid, it is challenged to present the secret string. If the secret string of the joining server matches the string in the catalog server, the joining server is accepted. If the string does not match, the join request is rejected.
Set the server properties file with JVM properties
Set the server properties file on the xs1 and xs2 servers. If you are not using the topology for this tutorial, set the server properties file on all of the application servers that you are using to host container servers.
- Open the Java virtual machine page for the server. Servers > Application servers > server_name > Java and Process Management > Process definition > Java Virtual Machine
- Add the generic JVM arguments:
- Click OK and save the changes.
Now the WebSphere eXtreme Scale server authentication is secured. By configuring this security, all the applications that try to connect to the WebSphere eXtreme Scale servers are required to provide a credential. In this tutorial, the WSTokenAuthenticator is the authenticator. As a result, the client is required to provide a WebSphere Application Server security token.
< Previous | Next >