ssl.init.svcstartcomplete.CWPKI0004I=CWPKI0004I: SSL service started successfully SSL service started. None. Informational only ssl.reinitialize.config.error.CWPKI0026E=CWPKI0026E: Error reinitializing the SSL configuration after a change to security.xml. The extended error message is "{0}". An exception occurred reading the SSL configurations from the security.xml after a change occurred. Review the exception message text and verify the SSL configuration parameters are valid. ssl.notification.send.info.CWPKI0037I=CWPKI0037I: Expiration monitor reports the following information: {0}. This is information regarding certificate expiration. May need to manage certificates to resolve the reported problems. ssl.signer.exchange.error.CWPKI0030E=CWPKI0030E: Error occurred exchanging signers between cell and node. The exception that occurred is: {0}. The DefaultKeyStores between cell and node will have exchange signers with corresponding DefaultTrustStores. An error occurred during this process. A manual signer exchange may need to take place. ssl.load.https.stream.handler.CWPKI0025E=CWPKI0025E: Could not load the https Handler class "{0}". The extended error message is {1}. There was a classloading error trying to load the HTTPS URLStreamHandler class. Check the SSL configuration to ensure the context provider is correct for the platform. 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}". The certificate alias specified for this SSL configuration is not in the specified KeyStore. Either add a certificate into the KeyStore with the specified certificate alias or change the specified certificate alias to match an alias found in the client KeyStore. ssl.signer.alias.not.found.CWPKI0305E=CWPKI0305E: The <aliasFromRemoteStore> specified as "{0}" was not found in truststore "{1}" on the server. The alias specified was not found in the truststore. Try issuing -listRemoteKeyStoreNames command to get the list of names. ssl.init.error.CWPKI0008E=CWPKI0008E: Error during SSL initialization. The exception is {0}. An unexpected error occurred during security initialization. This is a general error. Look for previous messages that may be related to the failure or a configuration problem. Enabling SSL=all=enabled debug trace may yield additional information. ssl.keystore.type.invalid.CWPKI0018W=CWPKI0018W: The keystore type of {0} is not valid for SSL config alias {1}. The keystore type configured is not correct. Change the keystore type in the SSL configuration. ssl.init.startcomplete.CWPKI0002I=CWPKI0002I: SSL service initialization completed successfully SSL service initialization completed successfully.. None. Informational only ssl.signer.no.signers.added.CWPKI0309I=CWPKI0309I: All signers from remote keystore already exist in local keystore. Indicates no signers needed to be added to the local keystore. None. 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}". The certificate alias specified for this SSL configuration is not in the specified KeyStore. Either add a certificate into the KeyStore with the specified certificate alias or change the specified certificate alias to match an alias found in the server KeyStore. 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}". The SSL context provider specified is not recognized as a valid context provider. Check the SSL configuration to ensure the correct SSL context provider is specified. ssl.signer.add.to.local.truststore.CWPKI0308I=CWPKI0308I: Adding signer alias "{0}" to local keystore "{1}" with the following SHA digest: {2} Indicates the signer being added to the local keystore. None. 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. When the server is running in FIPS mode the IBMJCEFIPS provider should be in the java.security file. The java.security file needs to be changed to include the IBMJCEFIPS provider in the provider list before the IBMJCE provider. 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}". An error occurred during the SSL handshake. It may require a signer export/import from the target host to the client TrustStore. Review the extended error message coming from the TrustManager to help determine what needs to change between the target SSL configuration and the client SSL configuration. ssl.keystore.load.error.CWPKI0033E=CWPKI0033E: The keystore located at "{0}" failed to load due to the following error: {1}. An error occurred while creating or opening the keystore. Check that the properties in the keystore configuration and ensure the keystore exists. 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}. The KeySet either does not have a keyGenerationClass defined, it cannot find the keyGenerationClass, a read-only KeyStore is associated with the KeySet, or the KeyStore does not allow the writing of secret keys. Modify the configuration so a proper keyGenerationClass is configured and a KeyStore type is configured with allows the writing of secret keys. ssl.init.nullprocesstype.CWPKI0010E=CWPKI0010E: Cannot obtain the WAS process type during initialization. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . ssl.signer.local.truststore.not.found.CWPKI0310E=CWPKI0310E: The <localKeyStoreName> specified as "{0}" was not found on the client. The local truststore is not found. Try issuing -listLocalKeyStoreNames command to get the list of names. ssl.client.config.parse.CWPKI0019E=CWPKI0019E: Error parsing the SSL client configuration file {0}. The error returned is {1}. There may be a problem with the syntax of the ssl.client.props file or the location of the file is invalid. Review the error returned and check the syntax and location of the ssl.client.props file. ssl.signer.retrieval.logfile.location.CWPKI0303I=CWPKI0303I: Trace is being logged to the following location: {0} Indicates where the mode is being logged. None. ssl.signer.remote.truststore.list.CWPKI0306I=CWPKI0306I: The following remote keystores exist on the specified server: {0} Indicates a list of the remote keystores. None. ssl.schedule.read.error.CWPKI0035E=CWPKI0035E: Schedule "{0}" could not read the next scheduled date. Initializing alarm for the following date: {1}. An error occurred reading the date from the schedule file in /etc. Ensure the /etc directory is writable or the file has not been modified. ssl.disable.url.hostname.verification.CWPKI0027I=CWPKI0027I: Disabling default hostname verification for HTTPS URL connections. Hostname verification will be disabled by default for URL connections. Hostname verification checks that the X509 Certificate Common Name (CN) matches the hostname it is from. To enable default JSSE URL hostname verification, set the com.ibm.ssl.performURLHostNameVerification property to true. 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}. Either the runtime could not find the key generation class configured for the KeySet or the class does not implement com.ibm.websphere.crypto.KeyGenerator or com.ibm.websphere.crypto.KeyPairGenerator. Check to ensure the key generation class configured is specified in a location which can be found by the WebSphere runtime. Check the InfoCenter on where to specify custom classes for the runtime to find them. ssl.expiration.expired.CWPKI0017E=CWPKI0017E: The certificate with alias {1} from keyStore {2} is expired. A certificate is expired in the keystore. Open the keystore and validate the expiration dates on all certificates in the keystore. Remove any expired certs. ssl.stop.error.CWPKI0015E=CWPKI0015E: Error stopping SSL component. The exception is {0}. An unexpected error occurred stopping the SSL component. This is a general error. Look for previous messages that may be related to the failure or a configuration problem. Enabling SSL=all=enabled debug trace may yield additional information. ssl.init.svcstart.CWPKI0003I=CWPKI0003I: SSL service is starting SSL service is starting. None. Informational only ssl.load.keymanager.error.CWPKI0021E=CWPKI0021E: Error loading custom key manager class {0}. The exception message is {1}. A class loading error occurred loading the custom key manager configured. Ensure the class can be found in the environment. ssl.signer.retrieval.logfile.error.CWPKI0302E=CWPKI0302E: Cannot write to the trace logfile at the following location: {0} Indicates there's a problem writing to the specified logfile. Change the logfile path or make sure the file specified is not in use. crypto.key.getkey.error.CWPKI0201E=CWPKI0201E: Error retrieving key alias {0} from KeySet {1}. The exception that occurred is: {2}. An error occurred while retrieving keys from the KeyStore for the specified KeySet. Check that the KeySet configuration is correct. ssl.cannot.find.node.from.hostlist.CWPKI0039E=CWPKI0039E: Cannot find Node connector properties for the hostname {0} in the hostlist for keystore {1}. Make sure the hostname entered is in the canonical format as it appears in serverindex.xml. Edit the hostlist to convert it to the proper canonical format. ssl.certificate.end.date.invalid.CWPKI0312E=CWPKI0312E: The certificate with subject DN {0} has an end date {1} which is no longer valid. The certificate has expired. Replace the certificate with a valid certificate. ssl.signer.local.truststore.list.CWPKI0307I=CWPKI0307I: The following local keystores exist on the client: {0} Indicates a list of the local keystores. None. ssl.init.startfail.CWPKI0005I=CWPKI0005I: SSL service initialization failed SSL service initialization failed None. Informational only ssl.notification.send.error.CWPKI0036E=CWPKI0036E: Error sending email to "{0}" using smtp server "{1}". The exception message is: "{2}". An error occuring sending email to the specified SMTP server. Ensure the SMTP server specified is valid and that your companies firewall policy allows sending to SMTP ports. 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}". The handshake protocol specified is not recognized as a valid handshake protocol. Check the SSL configuration to ensure the right handshake protocol is specified. 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. This message is for providing options for the client to retrieve signers needed for a successful SSL connection. Either run retrieveSigners or enable the signer exchange prompt to correct the problem. ssl.loadresource.error.CWPKI0011E=CWPKI0011E: Failed to load {0} resource from cell. The exception is {1} The specified resource could not be loaded due to an exception. The failure may be related to a configuration problem related to the resource. ssl.init.startinit.CWPKI0001I=CWPKI0001I: SSL service is initializing the configuration SSL service is initializing the configuration. None. Informational only ssl.default.password.in.use.CWPKI0041W=CWPKI0041W: One or more key stores are using the default password. Default key store passwords should be changed when possible. Change all key store passwords either using AdminConsole or IKeyMan. ssl.client.keystore.create.error.CWPKI0031E=CWPKI0031E: Error creating a client keystore or truststore during initialization. The exception that occurred is: {0}. An error occurred while creating the file-based keystore or truststore during process initialization. Check that the keystore or truststore settings are valid. Verify the keystore or truststore settings in the ssl.client.props. ssl.init.mbeanerror.CWPKI0006E=CWPKI0006E: Error creating or registering {0} mBean. The exception is {1} An unexpected exception occurred when trying to create or register an mBean. There may be a problem with the configuration. The exception may include details. ssl.signer.remote.truststore.not.found.CWPKI0304E=CWPKI0304E: The <remoteKeyStoreName> specified as "{0}" was not found on the server. The remote truststore is not found. Try issuing -listRemoteKeyStoreNames command to get the list of names. ssl.signer.general.error.CWPKI0314E=CWPKI0314E: The following error is returned from an exception: {0} Check the command line to ensure the options are correct. Check the usage help and retry after correcting the option. ssl.init.svcstartfail.CWPKI0007I=CWPKI0007I: SSL service failed to start successfully SSL service did not start. None. Informational only crypto.key.import.error.CWPKI0203E=CWPKI0203E: An attempt to import keys to KeySet {0} failed. The detailed message is: {1}. The keys passed in may not have been correctly formed or the keystore could not be accessed to store them. Attempt to determine the cause based on the exception and adjust the configuration as needed. ssl.signer.retrieval.tracemodeon.CWPKI0301I=CWPKI0301I: Trace mode is on. Indicates trace mode is on. None. 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. The start date of the certificate is not valid. Ensure that the client's clock matches up with the server's clock. Otherwise, create a certificate with the proper start date. ssl.expiration.monitor.start.error.CWPKI0038E=CWPKI0038E: Expiration monitor failed to start with the following error: {0}. A problem occurred starting the expiration monitor command task. Try starting the expiration monitor explicitly to determine more information about the error. ssl.self.signed.create.error.CWPKI0032E=CWPKI0032E: Error creating a self-signed certificate. The exception that occurred is: {0}. An error occurred while creating a self-signed certificate during process startup. Check that the default self-signed certificate property values (com.ibm.ssl.defaultCertReq*) are valid. ssl.init.nullsecobject.CWPKI0009E=CWPKI0009E: Cannot create security object during initialization. Cannot create the security object from repository. Internal Error. The security.xml might be corrupted or missing. Contact your service representative. crypto.key.auto.generate.error.CWPKI0204E=CWPKI0204E: An error occurred during a scheduled key generation for KeySetGroup {0}. The detailed error message is: {1}. A problem occurred while a new key reference was created for the KeySetGroup specified. After the key reference was created in the configuration the key was generated. One of these steps failed. Attempt to determine the cause based on the exception and adjust the configuration as needed. ssl.init.ssldm.init.CWPKI0014I=CWPKI0014I: The SSL component''s FFDC Diagnostic Module {0} registered successfully: {1}. Describes whether or not the SSL component's FFDC Diagnostic module was successfully registered. None. Informational only. 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] Usage information on the parameters for executing this script. None. ssl.load.trustmanager.error.CWPKI0020E=CWPKI0020E: Error loading custom trust manager class {0}. The exception message is {1}. A class loading error occurred loading the custom trust manager configured. Ensure the class can be found in the environment. ssl.schedule.init.error.CWPKI0034E=CWPKI0034E: Schedule "{0}" could not be initialized because of the following error: "{1}". An error occurred initializing the schedule. Check that the properties for the scheduler are valid. Ensure the /etc directory is writable. ssl.fips.enabled.CWPKI0012I=CWPKI0012I: FIPS is enabled. The server is running in FIPS mode, using the IBMJCEFIPS provider. No user action is required. ssl.signer.invalid.option.CWPKI0313W=CWPKI0313W: The following option is not valid: {0} Check the command line to ensure the options are correct. Check the usage help and retry after correcting the option. ssl.expiration.warning.CWPKI0016W=CWPKI0016W: The certificate with alias {0} from keyStore {1} will be expired in {2} days. A certificate is about to expire in the keystore. Open the keystore and validate the expiration dates on all certificates in the keystore. Prepare to generate new certificates, if necessary.