SSLC

SSLC0001W: {0} in an invalid security level. Default of high will be used.

Explanation

Valid values for security level are low, medium and high.

Action

Ensure that the security level is set to a valid value.

SSLC0002E: The SSL channel cannot be started due to the following incorrect settings: {0}

Explanation

One or more settings for security in the SSL channel were not valid.

Action

The SSL channel security settings should be modified to the correct values.

SSLC0003E: Alias {0} does not map to a known security repertoire.

Explanation

If a configuration 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.

SSLC0004W: FIPS support has been requested, but the specified provider {0} might not support it.

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.

SSLC0005E: Unable to get a PKCS keystore.

Explanation

The token information provided did not identify a valid PKCS keystore.

Action

Review and update the token information to identify a valid PKCS keystore.

SSLC0006E: Error reading the SSL channel configuration, exception: {0}

Explanation

An exception was created when reading the SSL channel configuration.

Action

Problems in the SSL channel configuration should be fixed.

SSLC0007W: The keystore or truststore type specified is invalid. Automatically adjusting to use the correct type, however, please correct the SSL configuration for performance reasons.

Explanation

The keystore or truststore type specified is not valid.

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.

SSLC0008E: The SSL connection cannot be initialized from the {1} host and {2} port on the remote client to the {3} host and {4} port on the local server. Exception: {0}

Explanation

A new connection failed to complete a successful secure handshake. The most common reason is that the client sent an unencrypted message to a secure port. Another common reason is that an SSL certificate expired.

Action

If the client sent an unencrypted message to a secure port, configure the client to use SSL, or to connect to a port on the application server that does not require SSL. Alternatively, check whether an SSL certificate expired. If it has, replace the expired SSL certificate with an unexpired one.

SSLC0009E: Hardware crypto is not supported.

Explanation

Support for hardware cryptography cards is not available.

Action

Change the security settings to disable the use of hardware cryptography.

SSLC0010E: Keystore file exists, but is empty: {0}

Explanation

The keystore from the configuration was found, but had no contents.

Action

Replace the current keystore file with valid keystore.

SSLC0011E: No keystore specified and no hardware crypto defined.

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.

SSLC0012E: Invalid truststore name of null.

Explanation

The truststore name is not present in the security configuration.

Action

Update the security settings to specify a valid truststore file.

SSLC0013E: Invalid password for keystore {0}. Internal exception {1}.

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.