Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

LDAP authentication causes SSLHandshakeException



Adding new signed certificates to the LDAP server causes authentication fail in PRPC.

Error Messages

2015-05-13 09:47:22,233 [   WebContainer : 12] [  STANDARD]  (edentials.Code_Security.Action) ERROR  - External authentication failed:
javax.naming.CommunicationException: simple bind failed:  [Root exception is PKIX path building failed: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is:
       The certificate issued by CN=ABC Root CA, O=ABC, L=Minneapolis, ST=Minnesota, C=US is not trusted; internal cause is:
       Certificate chaining error]
                at com.sun.jndi.ldap.LdapClient.authenticate(
                at com.sun.jndi.ldap.LdapCtx.connect(
                at com.sun.jndi.ldap.LdapCtx.<init>(
                at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(
                at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(
                at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(
                at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(
                at javax.naming.spi.NamingManager.getInitialContext(
                at javax.naming.InitialContext.initializeDefaultInitCtx(
                at javax.naming.InitialContext.getDefaultInitCtx(
                at javax.naming.InitialContext.internalInit(
                at javax.naming.InitialContext.<init>(
                at com.pegarules.generated.activity.ra_action_ldapverifycredentials_f96375d061d529a311d26e4c464308cd.step4_circum0(

Steps to Reproduce

Authenticate into PRPC using LDAP over LDAP server.

Root Cause

The root cause of this problem is in a third-party product. The SSL connectivity between the Pega node and the LDAP server is broken. This error indicates that the signer root and intermediate certificates from the specified target host (LDAP server) have not been installed in the client Pega node’s (JVM’s) truststore.

When using the certificate from another entity (JVM), make sure to use the certificate chain to obtain the root CA certificate. The certificate chain, also known as the certification path, is a list of certificates used to authenticate an entity (JVM). The chain, or path, begins with the certificate of that entity, and each certificate in the chain is signed by the entity identified by the next certificate in the chain. The chain terminates with a root CA certificate. The root CA certificate is always signed by the CA itself. The signatures of all certificates in the chain must be verified until the root CA certificate is reached.


This issue is resolved by making the following change to the operating environment:

Ensure that the signer root and the intermediate certificates are imported into IBM Websphere JVM’s truststore that Pega application is running on.

Published June 12, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us