Server Certificate Could Not Be Verified Because The Following Self-signed Certificate Is Not In The
(Doc ID 2539039.1)
Last updated on MAY 04, 2023
Applies to:
Oracle Agile Product Collaboration - Version 9.3.6.0 and laterInformation in this document applies to any platform.
Symptoms
Users are getting un-trusted error message from the Java client and unable to download files from the web client due to lack of certificate trust.
<BEA-090908> <Using the default WebLogic SSL Hostname Verifier implementation.>
javax.naming.CommunicationException: Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3s://xxxx.xxx.xx:443: Destination xxxx.xxxx.xxxx.xxxx, 443 unreachable.; nested exception is:
javax.net.ssl.SSLHandshakeException: General SSLEngine problem; No available router to destination.; nested exception is:
javax.net.ssl.SSLHandshakeException: General SSLEngine problem; No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination.]
at weblogic.jndi.WLInitialContextFactoryDelegate.throwRetryException(WLInitialContextFactoryDelegate.java:467)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:403)
at weblogic.jndi.Environment.getContext(Environment.java:353)
at weblogic.jndi.Environment.getContext(Environment.java:322)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:131)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
Customer has re-generate the SSL certificate and re-import using instruction from Note 569235.1, but users still get same error.
Agile Acollect reports the below error and warning:
Server Certificate Could Not Be Verified because the following self-signed certificate is not in the trust keystore
<Warning> <oracle.jps.keystore> <BEA-000000> <**************************************************************
* Demonstration CA was found in use in this environment. *
* This deployment may be vulnerable to security attacks. *
* Replace the Demonstration CA with a custom CA immediately. *
****************************************************************>
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |