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

Issue with TLS version 1.2 support for SOAP Connectors



User is integrating their internal systems with PRPC environment. They have configured SOAP Connector in PRPC to access an external SOAP Service (secured strictly with TLS v1.2). On executing the SOAP Connector, user was encountering " Received fatal alert" error.

Error Messages Received fatal alert: handshake_failure
       at Source)

Steps to Reproduce

1. Setup a SOAP Service secured with TLS v1.2 with 2 way SSL setup.
2. Create a SOAP Connector in PRPC and connect to this external secured SOAP Service created above.

Root Cause

This has been identified as an issue in Pega 7.1.6. This has been fixed Pega 7.1.7.


Suggested a local change - save-as out-of-the-box activity InvokeAxis2 in application ruleset and update following Java code snippet in the step-8 -

Code Before Fix :
 } else if(keyStorePageSSL != null && trustStorePage != null) {
 if(keyStoreBytes != null)
 tsInputStream = new;
 if(trustStoreBytes != null)
 ksInputStream= new;

Code After Fix :
 } else if(keyStorePageSSL != null && trustStorePage != null) {
 if(keyStoreBytes != null)
 ksInputStream = new;
 if(trustStoreBytes != null)
 tsInputStream = new;

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?

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