Why can't I set integrated authentication anymore when consuming a SOAP webservice?

Hi all,

Since the latest platform upgrade (I think?) the way to set up the consumption of SOAP webservices has changed.

In the past, when implementing the consumption of a SOAP webservice one could set a flag called Integrated authentication to YES. This worked fine. 

But now it it is no longer possible to set this flag, which makes implementing a SOAP webservice that use windows authentication a lot more difficult.

The error I am getting is :

The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Negotiate,NTLM'.


Can anyone tell me why it is no longer possible to easily set Integrated authentication, when implementing a SOAP webservice in OutSystems?

And is there an easy way to get this working when I try to consume a webservice outside OutSystems that requires Windos authentication?


Regards, Robert


For a variety of reasons, this functionality was removed from the platform. It can be implemented via SOAP extensibility:

https://success.outsystems.com/Documentation/11/Reference/OutSystems_APIs/SOAP_Extensibility_API

https://success.outsystems.com/Documentation/11/Extensibility_and_Integration/SOAP/Consuming_SOAP_Web_Services/Use_Advanced_Extensibility ... there are several examples under this node in the docs, one of which shows client certificate authentication, which would probably be a good jumping off point for doing integrated auth.

https://docs.microsoft.com/en-us/dotnet/api/system.servicemodel.httpclientcredentialtype?view=netframework-4.8

Above shows the enumeration needed to set the auth credential type.

Hope that helps.