You might have errors returned when you are trying to configure Secure Sockets Layer (SSL) for encrypted access. This article describes some of the common errors you might encounter and makes suggestions on how to fix the problems.
If you do not see a problem that resembles yours, or if the information provided does not solve your problem, contact IBM support for further assistance.
"The Java Cryptographic Extension (JCE) files were not found. Please check that the JCE files have been installed in the correct directory."When you click OK, the iKeyman tool closes. To resolve this problem:
For
example, the command is similar to: export JAVA_HOME=/opt/WebSphere/AppServer/java
If WebSphere Application Server is installed on your c:
drive, the command would be: set JAVA_HOME=c:\WebSphere\AppServer\java
The file is located in the install_dir/java/jre/lib/ext/ directory.
By default, the file is located in the following directory: app_server_rootedition_name/java/ext.
You might receive the following error when the keystore password is not being used correctly.
CWPKI0033E: The keystore located at "C:/WebSphere/AppServer/profiles/AppSrv01/etc/trust.p12" failed to load due to the following error: Unable to verify MAC.
Change the Password field that references this keystore by using the correct password. The default password is WebAS. Never use this password in a production environment.
CWPKI0022E: SSL HANDSHAKE FAILURE: A signer with SubjectDN "CN=BIRKT40.austin.ibm.com, O=IBM, C=US" was sent from target host:port "9.65.49.131:9428".
The signer might need to be added to the local truststore C:/WASX_c0602.31/AppServer/profiles/Dmgr09/etc/trust.p12 that is located in the SSL configuration alias DefaultSSLSettings. The truststore is loaded from the SSL configuration file.
"No trusted certificate found."
This error indicates that the signer certificate from the specified target host and port has not been located in the specified truststore, the SSL settings, and the SSL configuration file. If this occurs in a client process, there are several things that you can do:
If this issue occurs in a server process, then complete one of the following procedures:
Prior to WebSphere Application Server Version 6.1, the WebSphere Application Server management processes allowed the individually-managed SSL configurations which were set by system properties. Your pre-Version 6.1 system properties settings were processed successfully.
With WebSphere Application Server Version 6.1, central management of Secure Sockets Layer (SSL) configuration occurs. Applications that use SSL connections based on values set for system properties instead of using the centrally managed default dynamic SSL configuration can experience handshake failures. Nodeagent to appserver communications is being governed by the default dynamic SSL configuration in WebSphere Application Server Version 6.1 and not through the system properties you set. You may need to adjust your application to use the centrally managed SSL configuration of WebSphere Application Server Version 6.1.
CWPKI0023E: The certificate alias "default" specified by the property com.ibm.ssl.keyStoreClientAlias is not found in KeyStore "c:/WebSphere/AppServer/profiles/Dmgr01/config/cells/myCell/key.p12".
This error indicates that the certificate alias that was specified cannot be found in the referenced keystore. Either change the certificate alias or make sure that alias exists in the specified keystore.