Skip to main content

Support Article

Peer not authenticated - SSLv3 issue



Your system is upgraded to Websphere Application Server (WAS) from 8.5. Users report not being able to run a member search after upgrade. 

Error Messages

The PegaRULES log file shows the below error: peer not authenticated.

2015-03-23 12:49:00,511 [ WebContainer : 5] [TABTHREAD4] [ MyApp:01.01.29] (nvoke.Rule_Connect_REST.Action) ERROR server1 - Caught unhandled exception: peer not authenticated

Steps to Reproduce


Root Cause

The root cause of this problem is in a third-party product.

There is a security issue with the use of SSLv3 communications. Please see IBM knowledge base article ID 1687173 for further information on the issue. 


This issue is resolved through the following Local-change:

The issue is related to IBM Message Broker use of SSLv3. Upgrade from IBM WebSphere Message Broker V7.0 (MB7) to MB9 to avoid the issue.
Suggest Edit

Published June 12, 2015 - Updated October 8, 2020

Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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