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 using valid NTLM credentials



While attempting to use provided operations from an Exchange Web Service (EWS) located on our client's network '', user is receiving an error stating that "peer not authenticated" when the credentials used are valid.

User is operating within the network environment where user has access and successful authentication to Microsoft Lync and Microsoft Outlook. The authentication error is causing a SOAP service failure and is keeping our team from being able to provide an Exchange integration for our client's application. The web service and NTLM authentication works successfully using third party software SoapUI.

Error Messages

peer not authenticated

Steps to Reproduce

Within a secure NTLM authenticated environment, attempt to use and access a web service that requires NTLM authentication.

Root Cause

The truststore used by the Websphere application server is different from where the user has imported the required certificates.
As per the system.out logs with the JVM flag, it is found WAS server is using the default JAVA Cacerts trust store file at the location

D:\Program Files (x86)\IBM\WebSphere\AppServer\java\jre\lib\security\cacerts 

However as per the custom configuration, it should be trust.p12, where user has imported the required certificates:



The WAS SSL property conglutination file is affecting the server to select the wrong trust store file. After correcting the property file to choose the correct truststore, the issue is resolved.


Published May 13, 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