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

SSLPeerUnverifiedException for Connect-REST



User has configured a two-way SSL between Pega and another system.

They exchanged certificates and the certificate of the Service that they were going to connect to (KYC) was configured in WebSphere's Trust Store (Container-Managed Certificate in Trust Store).

User was getting in the logs and test connection fails.

Error Messages Caught unhandled exception: peer not authenticated
at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_ea5a601f5c30c4d8bb2e5da269e20397.step5_circum0(
at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_ea5a601f5c30c4d8bb2e5da269e20397.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at com.pegarules.generated.activity.ra_action_invoke_6a91441c4f6e5048b63360383ae1b952.step7_circum0(
at com.pegarules.generated.activity.ra_action_invoke_6a91441c4f6e5048b63360383ae1b952.perform(

Steps to Reproduce

1) Create a connect-REST Rule to connect with a System (KYC) using JSON.
2) Ensure that the End-point URL is secured and starts HTTPS.
3) Ensure that the KYC's Certificate is Configured in Pega's WebSphere App Server's Trust Store.
4) Make sure that the WebSphere App Server's Certificate is Configured in the KYC's JBOSS Server as well.
5) Test the connection. Observe that the exception.

Root Cause

Pega supports two-way SSL for all Connectors that supports SSL in any form.

Pega have not exhaustively tested 2-way SSL for every Connector type that supports it on every available platform, but there is no known limitation that would prevent it from working, if configured correctly.

A defect or configuration issue in the operating environment. The private key password was incorrect inside the keystore.


User has to check private key password and Keystore password are same or different.
User is suggested to try with the same password for the Keystore and the Private key.


Published October 13, 2016 - Updated October 8, 2020

Was this useful?

100% 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