Support Article
NTLM Auth failed: 401 Error: HTTP/1.1 401 Unauthorized
SA-17457
Summary
NTLMv2 authentication fails when using Connect-SOAP to invoke an Exchange Webservice.
Error Messages
2015-12-01 21:44:29,990 [http-apr-8718-exec-6] [ STANDARD] [ ] [ Employee:01.01.01] (ngineinterface.service.HttpAPI) ERROR localhost|127.0.0.1 your_op@org - 127.0.0.1: com.pega.pegarules.pub.PRRuntimeError
com.pega.pegarules.pub.PRRuntimeError: PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:712)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivitiesAlt(PRThreadImpl.java:461)
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.runActivities(HttpAPI.java:3322)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:385)
...
Caused by: com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed
at com.pegarules.generated.activity.ra_action_invokeaxis2_e0a499f26a95053ac6300b525bd7d41f.step15_circum0(ra_action_invokeaxis2_e0a499f26a95053ac6300b525bd7d41f.java:3994)
at com.pegarules.generated.activity.ra_action_invokeaxis2_e0a499f26a95053ac6300b525bd7d41f.perform(ra_action_invokeaxis2_e0a499f26a95053ac6300b525bd7d41f.java:308)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3500)
...
... 45 more
Caused by: com.pega.apache.axis2.AxisFault: Transport error: 401 Error: HTTP/1.1 401 Unauthorized
at com.pega.apache.axis2.transport.http.ComponentsHTTPSender.handleResponse(ComponentsHTTPSender.java:283)
at com.pega.apache.axis2.transport.http.ComponentsHTTPSender.doSend(ComponentsHTTPSender.java:208)
Steps to Reproduce
- Configure NTLMv2 authentication for your webservice
- Invoke Connect-SOAP to connect to Exchange web service with Authentication profile set up for NTLM
Root Cause
A defect or configuration issue in the operating environment. The machine hosting Pega 7 from where the Connect-SOAP calls were being made was in a different domain from the exchange webservice.
Resolution
Make the following change to the operating environment: Configure the machine hosting Pega 7 from where the Connect-SOAP calls are being made in the same domain as the Exchange webservice.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.