CWPKI

CWPKI0001I
ssl.init.startinit.CWPKI0001I=CWPKI0001I: SSL service is initializing the configuration
CWPKI0002I
ssl.init.startcomplete.CWPKI0002I=CWPKI0002I: SSL service initialization completed successfully
CWPKI0003I
ssl.init.svcstart.CWPKI0003I=CWPKI0003I: SSL service is starting
CWPKI0004I
ssl.init.svcstartcomplete.CWPKI0004I=CWPKI0004I: SSL service started successfully
CWPKI0005I
ssl.init.startfail.CWPKI0005I=CWPKI0005I: SSL service initialization failed
CWPKI0006E
ssl.init.mbeanerror.CWPKI0006E=CWPKI0006E: Error creating or registering {0} mBean. The exception is {1}
CWPKI0007I
ssl.init.svcstartfail.CWPKI0007I=CWPKI0007I: SSL service failed to start successfully
CWPKI0008E
ssl.init.error.CWPKI0008E=CWPKI0008E: Error during SSL initialization. The exception is {0}.
CWPKI0009E
ssl.init.nullsecobject.CWPKI0009E=CWPKI0009E: Cannot create security object during initialization.
CWPKI0010E
ssl.init.nullprocesstype.CWPKI0010E=CWPKI0010E: Cannot obtain the WAS process type during initialization.
CWPKI0011E
ssl.loadresource.error.CWPKI0011E=CWPKI0011E: Failed to load {0} resource from cell. The exception is {1}
CWPKI0012I
ssl.fips.enabled.CWPKI0012I=CWPKI0012I: FIPS is enabled.
CWPKI0013W
ssl.checkProviderList.warning.CWPKI0013W=CWPKI0013W: FIPS is enabled but the IBMJCEFIPS provider is not active in the java.security file. To ensure FIPS algorithms usage for all WAS process types, uncomment the IBMJCEFIPS provider in the java.security file, ahead of the IBMJCE, and renumber the provider list in sequential order.
CWPKI0014I
ssl.init.ssldm.init.CWPKI0014I=CWPKI0014I: The SSL component''s FFDC Diagnostic Module {0} registered successfully: {1}.
CWPKI0015E
ssl.stop.error.CWPKI0015E=CWPKI0015E: Error stopping SSL component. The exception is {0}.
CWPKI0016W
ssl.expiration.warning.CWPKI0016W=CWPKI0016W: The certificate with alias {0} from keyStore {1} will be expired in {2} days.
CWPKI0017E
ssl.expiration.expired.CWPKI0017E=CWPKI0017E: The certificate with alias {1} from keyStore {2} is expired.
CWPKI0018W
ssl.keystore.type.invalid.CWPKI0018W=CWPKI0018W: The keystore type of {0} is not valid for SSL config alias {1}.
CWPKI0019E
ssl.client.config.parse.CWPKI0019E=CWPKI0019E: Error parsing the SSL client configuration file {0}. The error returned is {1}.
CWPKI0020E
ssl.load.trustmanager.error.CWPKI0020E=CWPKI0020E: Error loading custom trust manager class {0}. The exception message is {1}.
CWPKI0021E
ssl.load.keymanager.error.CWPKI0021E=CWPKI0021E: Error loading custom key manager class {0}. The exception message is {1}.
CWPKI0022E
ssl.client.handshake.error.CWPKI0022E=CWPKI0022E: SSL HANDSHAKE FAILURE: A signer with SubjectDN "{0}" was sent from target host:port "{1}". The signer may need to be added to local trust store "{2}" located in SSL configuration alias "{3}" loaded from SSL configuration file "{4}". The extended error message from the SSL handshake exception is: "{5}".
CWPKI0023E
ssl.client.alias.not.found.CWPKI0023E=CWPKI0023E: The certificate alias "{0}" specified by the property com.ibm.ssl.keyStoreClientAlias is not found in KeyStore "{1}".
CWPKI0024E
ssl.server.alias.not.found.CWPKI0024E=CWPKI0024E: The certificate alias "{0}" specified by the property com.ibm.ssl.keyStoreServerAlias is not found in KeyStore "{1}".
CWPKI0025E
ssl.load.https.stream.handler.CWPKI0025E=CWPKI0025E: Could not load the https Handler class "{0}". The extended error message is {1}.
CWPKI0026E
ssl.reinitialize.config.error.CWPKI0026E=CWPKI0026E: Error reinitializing the SSL configuration after a change to security.xml. The extended error message is "{0}".
CWPKI0027I
ssl.disable.url.hostname.verification.CWPKI0027I=CWPKI0027I: Disabling default hostname verification for HTTPS URL connections.
CWPKI0028E
ssl.no.such.algorithm.CWPKI0028E=CWPKI0028E: SSL handshake protocol "{0}" is not valid. This protocol is specified in the SSL configuration alias "{1}" loaded from SSL configuration file "{2}". The extended error message is: "{3}".
CWPKI0029E
ssl.invalid.context.provider.CWPKI0029E=CWPKI0029E: SSL context provider "{0}" is not valid. This provider is specified in the SSL configuration alias "{1}" loaded from SSL configuration file "{2}". The extended error message is: "{3}".
CWPKI0030E
ssl.signer.exchange.error.CWPKI0030E=CWPKI0030E: Error occurred exchanging signers between cell and node. The exception that occurred is: {0}.
CWPKI0031E
ssl.client.keystore.create.error.CWPKI0031E=CWPKI0031E: Error creating a client keystore or truststore during initialization. The exception that occurred is: {0}.
CWPKI0032E
ssl.self.signed.create.error.CWPKI0032E=CWPKI0032E: Error creating a self-signed certificate. The exception that occurred is: {0}.
CWPKI0033E
ssl.keystore.load.error.CWPKI0033E=CWPKI0033E: The keystore located at "{0}" failed to load due to the following error: {1}.
CWPKI0034E
ssl.schedule.init.error.CWPKI0034E=CWPKI0034E: Schedule "{0}" could not be initialized because of the following error: "{1}".
CWPKI0035E
ssl.schedule.read.error.CWPKI0035E=CWPKI0035E: Schedule "{0}" could not read the next scheduled date. Initializing alarm for the following date: {1}.
CWPKI0036E
ssl.notification.send.error.CWPKI0036E=CWPKI0036E: Error sending email to "{0}" using smtp server "{1}". The exception message is: "{2}".
CWPKI0037I
ssl.notification.send.info.CWPKI0037I=CWPKI0037I: Expiration monitor reports the following information: {0}.
CWPKI0038E
ssl.expiration.monitor.start.error.CWPKI0038E=CWPKI0038E: Expiration monitor failed to start with the following error: {0}.
CWPKI0039E
ssl.cannot.find.node.from.hostlist.CWPKI0039E=CWPKI0039E: Cannot find Node connector properties for the hostname {0} in the hostlist for keystore {1}.
CWPKI0040I
ssl.handshake.failure.info.CWPKI0040I=CWPKI0040I: An SSL handshake failure occurred from a secure client. The server's SSL signer has to be added to the client's trust store. A retrieveSigners utility is provided to download signers from the server but requires administrative permission. Check with your administrator to have this utility run to setup the secure enviroment before running the client. Alternatively, the com.ibm.ssl.enableSignerExchangePrompt can be enabled in ssl.client.props for "DefaultSSLSettings" in order to allow acceptance of the signer during the connection attempt.
CWPKI0041W
ssl.default.password.in.use.CWPKI0041W=CWPKI0041W: One or more key stores are using the default password.
CWPKI0200E
crypto.key.generate.configuration.error.CWPKI0200E=CWPKI0200E: An attempt to generate keys using KeySet {0} occurred when the KeySet is not configured to generate keys. The detailed message is: {1}.
CWPKI0201E
crypto.key.getkey.error.CWPKI0201E=CWPKI0201E: Error retrieving key alias {0} from KeySet {1}. The exception that occurred is: {2}.
CWPKI0202E
crypto.key.generate.class.load.error.CWPKI0202E=CWPKI0202E: An error occurred trying to instantiate the key generation class {0} configured in KeySet {1}. The detailed message is: {2}.
CWPKI0203E
crypto.key.import.error.CWPKI0203E=CWPKI0203E: An attempt to import keys to KeySet {0} failed. The detailed message is: {1}.
CWPKI0204E
crypto.key.auto.generate.error.CWPKI0204E=CWPKI0204E: An error occurred during a scheduled key generation for KeySetGroup {0}. The detailed error message is: {1}.
CWPKI0300I
ssl.signer.retrieval.usage.CWPKI0300I=CWPKI0300I: Use the -listRemoteKeyStoreNames and -listLocalKeyStoreNames options to get list of names for <remoteKeyStoreName> and <localKeyStoreName>, respectively. Usage: retrieveSigners <remoteKeyStoreName> <localKeyStoreName> [options] options: [-profileName <profileName>] [-remoteAlias <aliasFromRemoteStore>] [-localAlias <storeAsAlias>] [-listRemoteKeyStoreNames] [-listLocalKeyStoreNames] [-autoAcceptBootstrapSigner] [-uploadSigners] [-host <host>] [-port <port>] [-conntype <RMI|SOAP>] [-user <user>] [-password <password>] [-trace] [-logfile <filename>] [-replacelog] [-quiet] [-help]
CWPKI0301I
ssl.signer.retrieval.tracemodeon.CWPKI0301I=CWPKI0301I: Trace mode is on.
CWPKI0302E
ssl.signer.retrieval.logfile.error.CWPKI0302E=CWPKI0302E: Cannot write to the trace logfile at the following location: {0}
CWPKI0303I
ssl.signer.retrieval.logfile.location.CWPKI0303I=CWPKI0303I: Trace is being logged to the following location: {0}
CWPKI0304E
ssl.signer.remote.truststore.not.found.CWPKI0304E=CWPKI0304E: The <remoteKeyStoreName> specified as "{0}" was not found on the server.
CWPKI0305E
ssl.signer.alias.not.found.CWPKI0305E=CWPKI0305E: The <aliasFromRemoteStore> specified as "{0}" was not found in truststore "{1}" on the server.
CWPKI0306I
ssl.signer.remote.truststore.list.CWPKI0306I=CWPKI0306I: The following remote keystores exist on the specified server: {0}
CWPKI0307I
ssl.signer.local.truststore.list.CWPKI0307I=CWPKI0307I: The following local keystores exist on the client: {0}
CWPKI0308I
ssl.signer.add.to.local.truststore.CWPKI0308I=CWPKI0308I: Adding signer alias "{0}" to local keystore "{1}" with the following SHA digest: {2}
CWPKI0309I
ssl.signer.no.signers.added.CWPKI0309I=CWPKI0309I: All signers from remote keystore already exist in local keystore.
CWPKI0310E
ssl.signer.local.truststore.not.found.CWPKI0310E=CWPKI0310E: The <localKeyStoreName> specified as "{0}" was not found on the client.
CWPKI0311E
ssl.certificate.before.date.invalid.CWPKI0311E=CWPKI0311E: The certificate with subject DN {0} has a start date {1} which is valid after the current date/time. This will can happen if the client''s clock is set earlier than the server''s clock. Please verify the clocks are in sync between this client and server and retry the request.
CWPKI0312E
ssl.certificate.end.date.invalid.CWPKI0312E=CWPKI0312E: The certificate with subject DN {0} has an end date {1} which is no longer valid.
CWPKI0313W
ssl.signer.invalid.option.CWPKI0313W=CWPKI0313W: The following option is not valid: {0}
CWPKI0314E
ssl.signer.general.error.CWPKI0314E=CWPKI0314E: The following error is returned from an exception: {0}