Configure hardware cryptographic devices for Web Services Security

Before we can use a hardware cryptographic device, configure and enable it. We must first configure a hardware cryptographic device using the SSL certificate and key management panels in the console. The key for the cryptographic operation can be stored in an ordinary Java keystore file and need not be stored on the hardware devices. After completing the alterations to the java.security file, as part of the following procedure, the cryptographic operations are enabled and the Java Virtual Machine (JVM) is able to select the hardware cryptographic device provider.

We must first configure a hardware cryptographic device using the SSL certificate and key management panels in the console.

Fix packs that include updates to the Software Development Kit (SDK) might overwrite unrestricted policy files. Back up unrestricted policy files before you apply a fix pack and reapply these files after the fix pack is applied.

For transitioning users: The unrestricted Java policy files are not required when using hardware cryptographic devices. These policy files were required in some earlier versions of the product.trns

1. In the console, click Servers > Server Types > WebSphere application servers and then select the server name.

2. Under Security, select JAX-WS and JAX-RPC security runtime.

3. Under Cryptographic Hardware, select Enable cryptographic operations on hardware device and then specify the name of the hardware cryptographic device configuration name. For more information, read about configuring a hardware cryptographic keystore.

4. Click OK.

5. (zos) Stop the application server.

6. (zos) Alter the java.security file.

   (iseries) The java.security file is located in the profile_root/properties directory.

   (dist) The java.security file is located in the app_server_root/java/jre/lib/security directory.

   (zos) The java.security file is located in the app_server_root/properties directory.

   The following changes need to be made to this file:

   1. Uncomment the following line of the file:
      #security.provider.1=com.ibm.crypto.hdwrCCA.provider.IBMJCECCA

   2. Reorder the list of providers and preference orders as follows:

      security.provider.1=com.ibm.crypto.hdwrCCA.provider.IBMJCECCA
      #security.provider.1=com.ibm.crypto.fips.provider.IBMJCEFIPS
      security.provider.2=com.ibm.crypto.provider.IBMJCE
      security.provider.3=com.ibm.jsse.IBMJSSEProvider
      security.provider.4=com.ibm.jsse2.IBMJSSEProvider2
      security.provider.5=com.ibm.security.jgss.IBMJGSSProvider
      security.provider.6=com.ibm.security.cert.IBMCertPath
      security.provider.7=com.ibm.security.sasl.IBMSASL
      security.provider.8=com.ibm.security.cmskeystore.CMSProvider
      security.provider.9=com.ibm.security.jgss.mech.spnego.IBMSPNEGO
      security.provider.9=com.ibm.xml.crypto.IBMXMLCryptoProvider
      security.provider.10=com.ibm.xml.enc.IBMXMLEncProvider
      security.provider.11=org.apache.harmony.security.provider.PolicyProvider

   The file structure and content are ready for use.

7. (zos) Start the application server. The cryptographic device is enabled for all Web service security applications that run on this application server.

Results

This procedure configures and enables a hardware cryptographic device for all Web Services Security applications running on this application server.

Related concepts

Hardware cryptographic device support for Web Services Security

Related tasks

Enable cryptographic keys stored in hardware devices in Web Services Security

Configure a hardware cryptographic keystore