WebSphere Process Server messages     Operating Systems: All supported

SSLC

SSLC0001W: {0} in an invalid security level. Default of high will be used.
Problem Valid values for security level are low, medium and high.
User response Ensure security level is set to a valid value.
SSLC0002E: The SSL channel cannot be started due to the following incorrect settings: {0}
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.
SSLC0003E: Alias {0} does not map to a known security repertoire.
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.
SSLC0004W: FIPS support has been requested, but the specified provider {0} may not support it.
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.
SSLC0005E: Unable to get a PKCS keystore.
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.
SSLC0006E: Error reading the SSL channel configuration, exeption: {0}
Problem An exception was thrown when reading the SSL channel configuration
User response Problems in the SSL channel configuration should be fixed.
SSLC0007W: The keystore or truststore type specified is invalid. Adjusting to use the correct type, however, please correct the SSL configuration for performance reasons.
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.
SSLC0008E: Unable to initialize SSL connection. Unauthorized access was denied or security settings have expired. Exception is {0}.
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.
SSLC0009E: Hardware crypto is not supported.
Problem Support for hardware cryptography cards is not available.
User response Change the security settings to disable the use of hardware cryptography.
SSLC0010E: Keystore file exists, but is empty: {0}
Problem The keystore from the configuration was found, but had no contents.
User response Replace the current keystore file with valid keystore.
SSLC0011E: No keystore specified and no hardware crypto defined.
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.
SSLC0012E: Invalid truststore name of null.
Problem The truststore name is not present in the security configuration.
User response Update the security settings to specify a valid truststore file.
SSLC0013E: Invalid password for keystore {0}. Internal exception {1}.
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.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.ssl.channel.resources.sslchannelmessages.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)