Last updated on MARCH 08, 2017
Applies to:Oracle Virtual Directory - Version 10.1.4.3 and later
Information in this document applies to any platform.
Oracle Virtual Directory (OVD) 10g / 10.1.4.3.0 or 11g.
When the remote / backend host server private key certificate is updated, the connection fails with error, for example:
javax.naming.CommunicationException: simple bind failed: myremotehost.mycompany.com:636 Root exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
Or for example, if the certificate expired:
javax.naming.CommunicationException: simple bind failed: <Backend Server IPaddress>:<SSL Port> [Root exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateExpiredException: NotAfter: Thu Jun 16 19:59:59 EDT 2011]
In 11g, the log may show:
javax.naming.CommunicationException: simple bind failed: host1.mycompany.com:2636 [Root exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target]
When this occurs the adapter does not failover to use the other remote nodes that are defined in the ldap adapter.
In looking to avoid this problem:
1. How to configure the adapter to failover to the other servers when the connection to the primary host fails due server private key certificate changes?
2. How to configure the adapters to use the Root Public key so the public keys do not need to be updated everytime the source private key certificate gets updated?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms