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 for Connect-HTTP



Connect-HTTP rule attempting to consume SSL-enabled service fails with a Peer Not Authenticated error in IBM Websphere application server, after certificates have been verified.

Error Messages

2016-06-28 12:07:28,302 [ WebContainer : 8] [ STANDARD] [ HMKCSDApp:02.01] (ector.Rule_Connect_HTTP.Action) ERROR <Server>|<IP>|Rule-Connect-HTTP.HMK-FW-CSD-Int-FindProvider-GeocodeResponse.TestGeocode lidc2ki - Caught unhandled exception: peer not authenticated peer not authenticated
at com.pega.apache.http.conn.ssl.AbstractVerifier.verify(


Steps to Reproduce

1.) Create a Connect-HTTP rule.
2.) Create an activity.
3.) Call the Connect rule from the activity.

Root Cause

A defect or configuration issue in the operating environment. The correct target server certificate was not present in the application server truststore hosting the Pega server. 


To resolve the issue, install the target server certificate into the truststore of the application server hosting the Pega server.

Published July 18, 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