Menu

#201 Authentication will not work

open
nobody
general (369)
5
2015-09-23
2007-10-05
Anonymous
No

I have an application on IIS6, the asmx WSDL will display perfectly through Internet Explorer 6 without prompting for credentials - when I try and enumerate the webservice through soapUI - it continues to prompt me for credentials.

Even when I put my valid domain credentials in - it continues to prompt me for credentials - until my Domain account gets locked out.

Discussion

  • Ole Lensmar

    Ole Lensmar - 2007-10-05

    Logged In: YES
    user_id=838515
    Originator: NO

    Hi!

    hm.. could you please check if you get the following in the soapUI log when required to enter your credentials;

    <host:port> requires Windows authentication

    Also, are you entering the username as <Domain>\\&lt;username> or just <username>?

    Sorry for the inconvenience..

    regards!

    /Ole
    eviware.com

     
  • Nobody/Anonymous

    Logged In: NO

    The site does require windows authentication, I do have an entry saying <host:80> requires windows authentication.

    The http log shows receiving the 401.2, 401.1 (which is the typical sequence in IIS 6.0) - and then a 401 (which should be a 200).

    The credentials I am giving to soapUI are the same credentials I used to log onto the machine. When bringing up the page in IE 6.0, the credentials are silently passed through and I can hit the WSDL interface of the service fine.

    I have tried using <domain\username> as the user name, as well as just using <username> and supplying domain in the [Domain] entry field below. I have also tried using a fully qualified UPN (user@fqdn.suffix), and that doesn't work either.

    Any help would be appreciated.

    Thanks!

     
  • Ole Lensmar

    Ole Lensmar - 2007-10-08

    Logged In: YES
    user_id=838515
    Originator: NO

    Hi!

    hmm.. what "should" work is entering just the username in the username field and just the domain in the domain field.. have you made any changes to the default HTTP Settings (for example turned on pre-emptive authentication)?

    What you could do to help is run your IE-request through TCP-Mon (or some other network sniffer; wireshark, netmon, etc..) to see the exact message-exchange for the IE request so we can compare with soapUIs requests..

    sorry for the inconvenience..

    regards!

    /Ole
    eviware.com

     
  • Nobody/Anonymous

    Logged In: NO

    So I shouldn't have to enter a password?

    I've tried it with both pre-emptive auth turned on, and off, and have tried it with a password and without - I get the same failures with SoapUI.

    The difference I can see in the trace on the NTLMSSP_AUTH request (where IE gets a response of 200 and SoapUI gets a response of 401):

    SoapUI doesn't have a NTLM Response in the NTLMSSP_AUTH request, but IE does.

    Inside the Authorization Header:

    SoapUI sets the Host Name to the remote host, IE sets the host name to the local machine

    SoapUI has flags of x00005206 IE has flags set of 0xa2888205

    User-Agents are different

    Order of Headers are different (SoapUI lists Authorization header first, then Host header), IE lists Host Header first than Authorization Header.

     
  • Aravind

    Aravind - 2015-09-23

    Hi
    Even i have the same issue. Every time I enter the username and password, it keeps popping up the same window. I am not able to pass through NTLM authentication. The same WSDL service works if it being called from a Web Application. Please suggest how to make it work. I have used Soap UI 3.6 and Soap UI 5.0 and in both of them I get "401: Unauthorized" error.

     

Log in to post a comment.