Replacing nusoap and curl using NTLM auth for sugar 12.0.3

Question

Hi, 
 We are upgrading a customer from 11.x to sugar 13, but in 12.0.3 Nusoap has been removed. The customer is also using NTLM authentication for their soap connection. I am having troubles finding documentation covering this scenario. I have found that we should replace Nusoap with the sugarcrm \SoapClient, but no clear documentation found how to implement this soapclient and wether it is possible to get NTLM authentication to work. 
 Besides NuSoap, the customer also uses curl with NTLM authentication, which should also be replaced I asume. 
 Any tips where to start? 
 Regards, 
 Stijn

Stijn Vermeulen · Answer

Hi Stijn Vermeulen , 
 Yes, we did remove Nusoap and advise everyone against using it. I'm assuming your NTLM auth is a custom code you need to rewrite for 13.0 is that correct? I would advise you to look into our native LDAP integration , if you are in SugarCloud, we have a few more options with SugarIdentity . If you need really need to rewrite your code, you could look into PHP's native SoapClient (I don't believe we have a Sugarcrm\SoapClient we support at this point). 
 You can create a client like: 
 $this->client = new \SoapClient(<your soap server> . '?wsdl', $params); 
 For cURL, you have to replace it with ExternalResourceClient .

Stijn Vermeulen · Answer

Hi Stijn Vermeulen , 
 ExternalResourceClient is our HTTP client, it is equivalent to cURL for Sugar, it doesn't have any logic in it other than dealing with HTTP transport, whatever you need to do in cURL, use ExternalResourceClient instead. 
 You can configure your Active Directory to accept LDAP authentication, so Sugar will use that connection to authenticate its users against. In fact, it will always be "outbound requests" as Sugar goes to LDAP and tried to authenticate (username+password) and LDAP provides a handshake with OK/NOK for those credentials.. 
 Perhaps you can explain better what you're trying to achieve so we can better assist you!?