We have few agents that communicate with other systems via and today at 13:00 we got such answer from Domino when we tried to set connection with external system. That was a huge problem for us since it affect our business.
It took some time to fix it, but here is a solution
javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.j: No trusted certificate found at com.ibm.jsse2.o.a(o.java:8) at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:549) at com.ibm.jsse2.kb.a(kb.java:355) at com.ibm.jsse2.kb.a(kb.java:130) at com.ibm.jsse2.lb.a(lb.java:135) at com.ibm.jsse2.lb.a(lb.java:368) at com.ibm.jsse2.kb.s(kb.java:442) at com.ibm.jsse2.kb.a(kb.java:136) at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:495) at com.ibm.jsse2.SSLSocketImpl.h(SSLSocketImpl.java:223) at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:724) at com.ibm.jsse2.SSLSocketImpl.startHandshake(SSLSocketImpl.java:81) at com.ibm.net.ssl.www2.protocol.https.c.afterConnect(c.java:8) at com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:20)
A Java application running on a Domino server connecting over SSL to another server may require having the SSL certificate authority of the other server imported into its JVM.
When a Java application running on a Domino server connects over SSL to another server, but does not have that server's trusted root certificates, an error may occur. One example of such an error is: HTTP JVM: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: No trusted certificate found.
The trusted root certificates that signed the remote server's SSL certificate must be also be trusted by the Domino server's JVM if a Java application is making an SSL connection.
Resolving the problemTo add the trusted root certificates to a Domino server JVM follow these steps:
A. Obtain the Certificate to be Imported
Each browser displays certificates in different ways, but they are usually quite similar. On the browser's URL bar, there is usually a zone that you can click on to display SSL certificate information. For example, you may see a padlock in the status bar, and clicking on the padlock opens the certificate information. Once the certificate information is open, click on the "Certification Path" informatino. There normally will be a way to export each of the signing certificates (trusted roots). Export the certifiers in the "Base-64 encoded X.509 (.CER)" format. The exported file in this format will be an ASCII text file that has "BEGIN CERTIFICATE" and "END CERTIFICATE" lines at the top and bottom. Once you have exported the certificates that signed the remote server's SSL certificate you can then import them into the JVM.
B. Import the SSL certifier into the JVM.
If Domino is on a UNIX server, perform these steps on a Windows workstation, and then move the cacerts to the server after the import is completed.Import the SSL Certificate into the JVM using these steps:
- Open a command line and change directory to C:\Lotus\Domino\jvm\bin.
- Run the batch file "IKEYMAN.exe" (a Java application will load).
- Click "Key Database File" then "Open".
- Browse to C:\Lotus\Domino\jvm\lib\security\cacerts. Note, you will have to view "All Files" to locate cacerts.
- Supply the default password of "changeit". Note, consult your administrator if you receive an error pertaining to the password.
- Select "Signer Certificates" in the drop-down menu.
- Click "Add"
- Select "Browse" and locate the .CER file you copied.
- Click "OK" and enter a descriptive label.
- On the Domino console issue the command "restart task http".
IBM Domino Java: No trusted certificate found. Fail?
Domino and No trusted certificate found
Disabling certificate validation in Java