Explanation | Valid values for security level are low, medium and high. |
Action | Ensure security level is set to a valid value. |
Explanation | One or more settings for security in the SSL channel were not valid. |
Action | SSL channel security settings should be modified to correct values. |
Explanation | If a config alias is specified on the SSL channel, it must map to a security repertoire. |
Action | The SSL channel configuration must be updated to reference a valid security repertoire. |
Explanation | Not enough information is available to determine if the specified provider is FIPS enabled. |
Action | Verify that the specified provider has the appropriate FIPS support. |
Explanation | Token information provided did not identify a valid PKCS keystore. |
Action | Review and update the token information to identify a valid PKCS keystore. |
Explanation | An exception was thrown when reading the SSL channel configuration |
Action | Problems in the SSL channel configuration should be fixed. |
Explanation | The keystore or truststore type specified is invalid. |
Action | Modify the SSL configuration so that the keystore or truststore type is a valid type. You can check the keystore and truststore types by loading them in WebSphere's IKeyMan tool. |
Explanation | A new connection failed to complete a successful secure handshake. |
Action | Check security settings. The certificate may have expired. Alternatively, an unauthorized client connection may have been denied. |
Explanation | Support for hardware cryptography cards is not available. |
Action | Change the security settings to disable the use of hardware cryptography. |
Explanation | The keystore from the configuration was found, but had no contents. |
Action | Replace the current keystore file with valid keystore. |
Explanation | A keystore or hardware cryptography setting is required in the security configuration, but neither exist. |
Action | Update the security settings to specify a keystore or to enable hardware cryptography. |
Explanation | The truststore name is not present in the security configuration. |
Action | Update the security settings to specify a valid truststore file. |
Explanation | The password provided for the keystore is not compatible. |
Action | Check the keystore password in the security settings, or specify a new keystore and password. |