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-REST error "peer not authenticated"



User is using Connect-REST with other environments and getting an error "peer not authenticated".
But, the server is authenticated, all SOAP web service calls are fine. This happens with the REST.

Error Messages

"peer not authenticated".
below error is seen in pegarules log, when issue is encountered.

Caused by: peer not authenticated
at com.pega.apache.http.conn.ssl.AbstractVerifier.verify(

Steps to Reproduce

Use Connect-REST on a server which is authenticated to call an end point which requires authentication.

Root Cause

In customer’s configuration, websphere endpoint is configured to provide the client certificates to service based on the endpoint address. Certificates are associated dynamically when the call is made by the containers. PRPC is using the apache client lib for the REST/HTTP calls which is not sending the client certificates for the REST/HTTP call.


This issue is resolved by HFix-9286 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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