WAS v8.5 > Reference > Sets
SSL certificate and key management
Use this page to configure security for Secure Socket Layer (SSL) and key management, certificates, and notifications. The SSL protocol provides secure communications between remote server processes or endpoints. SSL security can be used for establishing communications inbound to and outbound from an endpoint. To establish secure communications, a certificate and an SSL configuration must be specified for the endpoint.
To view this dmgr console page, click Security > SSL certificate and key management.
Configuration settings
Following dmgr console tasks:
- Manage endpoint security configurations
- Manage certificate expiration
Use Federal Information Processing Standard (FIPS) algorithms
Specifies the Federal Information Processing Standard (FIPS)-compliant Java cryptography engine is enabled.
- Does not affect the SSL cryptography that is performed by the application server for z/OS System Secure Sockets Layer (SSSL).
- Does not change the JSSE provider if this cell includes any Application Server versions before the application server for z/OS v6.0.x.
When you select the Use the Federal Information Processing Standard (FIPS) option, the LTPA implementation uses IBMJCEFIPS. IBMJCEFIPS supports the Federal Information Processing Standard (FIPS)-approved cryptographic algorithms for Data Encryption Standard (DES), Triple DES, and Advanced Encryption Standard (AES). Although the LTPA keys are backwards compatible with prior releases of the application server, the LTPA token is not compatible with prior releases. In prior releases, the application server did not generate the LTPA token using a FIPS-approved algorithm.
The IBMJSSE2 JSSE provider does not perform cryptographic functions directly, and therefore does not need to be FIPS-approved. Instead, the IBMJSSE2 JSSE provider uses the JCE framework for cryptographic functions and uses IBMJCEFIPS when FIPS mode is enabled.
. However, the IBMJSSE2 provider, which uses IBMJCEFIPS, is supported on the HP-UX platform.
| Information | Value |
|---|---|
| Default: | Disabled |
Dynamically update the runtime when SSL configuration changes occur
Specifies that all of the SSL-related attributes and LTPA keys that change must be read from the configuration dynamically after they have been saved, then reused for new connections. To avoid customer impact, IBM recommends that changes to production servers be made during off-peak periods.
| Information | Value |
|---|---|
| Default: | Enabled |
When this option is selected, the configuration is updated each time you configure an SSL communication.
Reference:
Manage endpoint security configurations
Manage certificate expiration settings
Notifications
SSL configurations page
Dynamic inbound and outbound endpoint SSL configurations page
Keystores and certificates page
Certificate authority (CA) client configuration collections
Key sets page
Key set groups page
Key managers page
Trust managers page
Default chained certificate configuration in SSL
AdminTask SecurityConfigurationCommands