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

Connect-SOAP does not work with SSL

SA-1306

Summary



After changing the EndPoint URL in the Connect SOAP rule from HTTP to HTTPS, the connectors stopped working and throws SSLHandshakeException in the log file.

Error Messages



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

Steps to Reproduce



1. Open Connect-SOAP rule and change the endpoint URL from HTTP to HTTPS
2. Execute the Connect SOAP rule using the connector activity which fails. 

Root Cause



In Connect-SOAP rule, user has changed the HTTP endpoint URL to HTTPS, which needs the configuration changes to Application Server.  And, the certificate to be placed in the truststore of the client which is using it. 

Resolution



After configuring SSL enabled web services, user was able to make the Connect-SOAP rule working without any issues. Refer PDN references - 
How-to-set-up-two-way-ssl-for-soap-over-http-using-rule-connect-soap 


 

Published January 31, 2016 - 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?

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