Hardware cryptographic device support for Web Services Security
In IBM WAS V6.1 or later, Web services security supports the use of cryptographic hardware devices. There are two ways in which to use hardware cryptographic devices with Web services security.
Enabling cryptographic operations on hardware devices
You can enable cryptographic operations on hardware devices. The keys that are used can be stored in a Java keystore file; it is not necessary to store them on the hardware device. The decision to use enable cryptographic operations on hardware devices is made at the server level only, not at the application level.
If cryptographic operations on hardware device is enabled, the Web service security runtime first attempts to use the hardware device for cryptographic operations. If the attempt to use the hardware device fails or if the algorithm is not supported by the hardware device, the runtime uses a software provider from the security providers list.
Enabling this feature might improve the performance, depending on the hardware device. For more information on how to enable cryptographic operations on hardware devices, see Configure hardware cryptographic devices for Web Services Security.
Secure keys
Cryptographic keys can be stored on the hardware cryptographic device and never leave the device. These secure keys are confined to the hardware cryptographic device for security considerations rather than performance considerations. The option to select whether to use keys that are stored in a hardware cryptographic device or a Java keystore file can be made at the application level.
If the keystore reference is specified to be a hardware device configuration, the Web services security runtime first attempts to obtain the cryptographic algorithm from the hardware device. If the algorithm is not supported or fails, the runtime uses a software provider from the security providers list.
For information on how to enable secure keys, see Enabling cryptographic keys stored in hardware devices in Web Services Security.
Limitations
The hardware cryptographic device support for Web Services Security currently has the following limitations:
- There is no support for a Web services client running as a J2EE Application Client.
- There is no support for hardware cryptographic devices on iSeries.
- Only V6.1 and later, Web services security applications can take advantage of the hardware cryptographic support.
Versions 5.x and 6.0.x Web services security applications can run in a V6.1 WebSphere Application Server, but these versions cannot take advantage of the hardware cryptographic support.
Long-term usage of session keys
You can configure WAS to use the hardware keystore, or you can configure the hardware acceleration card to allow the long-term usage of session keys. Session keys might be insecure.
If you are concerned about insecure session keys, configure WebSphere Application Server to use the hardware keystore. See the information about how to enable cryptographic keys that are stored in hardware devices in Web services security. To configure the hardware acceleration card to allow the long-term usage of session keys, see the manufacturer’s documentation for the specific hardware acceleration card. For example:
- For the nCipher nforce 1600 server V2.23.6, follow the nCipher documentation instructions.
- You can set the CKNFAST_SECURITY_ASSURANCES_OVERRIDE=longterm parameter in the cknfastrc configuration file. This configuration change eliminates the time limit that is associated with session keys.
- Follow the documentation for Cipher to restart the nCipher server.
- Restart WAS.
Related concepts
Overview of platform configuration and default bindings
Related tasks
Enabling hardware cryptographic devices for Web Services Security
Configure hardware cryptographic devices for Web Services Security
Enabling cryptographic keys stored in hardware devices in Web Services Security