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

"Peer not authenticated" error when connecting to REST service

SA-351

Summary



Run a connection test on a Connect-SOAP, Connect-REST, or other Connect rule configured for two-way SSL as explained in the PDN Article, How to set up two-way SSL for SOAP over HTTP using Rule-Connect-SOAP. See the "peer not authenticated" error.

Error Messages



ERROR: com.pega.pegarules.pub.services.ConnectorException: Caught unhandled exception: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated

Steps to Reproduce



Test the Connect-SOAP rule using the activity created by the Integration wizard.

Root Cause



A defect or misconfiguration in the PRPC operating environment
For the case reported, several required JVM arguments were missing from the environment.



Resolution



Perform the following local-change to the PRPC operating environment.
Add the following JVM arguments to the environment:

-Djavax.net.ssl.keyStore=C:/tomcat/client_keystore.keystore
-Djavax.net.ssl.keyStorePassword=client_keystore_pw_mypassword

-Djavax.net.ssl.trustStore= C:/tomcat/client_truststore.keystore
-Djavax.net.ssl.trustStorePassword= client_truststore_pw_mypassword

Published April 17, 2017 - 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