+1  A: 

I think SoapUI might only support NT authentication for the WSDL.

you can see some detail of how it is implemented here:

(BTW, this google search doesn't look promising for you!)

Colin Pickard
+4  A: 

SoapUI doesn't seem to work directly with NTLM authentication, but you can use a proxy such as Burp Suite to do the auth for you.

  1. Download Burp Suite from http://www.portswigger.net/suite/ and crank it up.
  2. On Burp's "Proxy : Intercept" tab, click the button to turn intercept off.
  3. On Burp's "Proxy : Options" tab, make sure it's set to an unused port, the default is 8081
  4. On Burp's "Comms" tab, tick "do www authentication" and add a setting for the server you wish to hit. Also tick "prompt for credentials on authentication failure"
  5. Switch to Burp's "Proxy : History" tab so you can see requests going through.
  6. In SoapUI, choose File > Preferences, then select "Proxy Settings". Enter Host "localhost" and port "8081".
  7. Use SoapUI as normal. It will send requests through Burp Proxy, which will do the NTLM authentication for you.
Mike Mason
Thanks for the response. This worked for me to query a Sharepoint list via soapUI.
Sarah Vessels
There is no "Comms" tab burp's current version.
Pedro Morte Rolo
The "Comms" tab is "Options" in the current version. Wish I could edit others' posts already ;-)
moontear
+1  A: 

Hi!

soapUI does natively supports NTLMv1, but since many newer NTLM-based installation require NTLMv2 this is a great workaround, thanks for posting!

/Ole eviware.com

olensmar
A: 

BurpSuite ProVersion has the 'do www authentication' area, not the freebie version. :(

aojaok44