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