none
Testing web service with SoapUI and Windows authentication RRS feed

  • Question

  • I've spent days searching for a solution to get a simple HTTP webservice, salesorder.read, working off of a JAVA client with no avail. We're trying to achieve communication first via NTLM as this was suggested in many forums, but I'm open to other suggestions. My testing criteria is to get it working on VS first, then SOAP UI and finally java. I've been successful at testing with VS, however I haven't had any luck with SOAP UI.

    Configuration:

    -AX 2012 R3

    - Changed HTTP configuration binding from Windows to NTLM (as suggested in many posts)

    - IIS

    - Authentication set to Windows and Basic Authentication

    - Windows authentication providers; NTLM set as primary

    - SOAP UI

    - Basic configuration w/ Authentication set to NTLM

    - Verified lmcompatibilitylevel set to 1 on server

    The response has ever been "An error occurred." or "401 - Unauthorized: Access is denied due to invalid credentials. You do not have permission to view this directory or page using the credentials that you supplied."

    • Tue Dec 20 11:06:41 EST 2016:DEBUG:Stale connection check
    • Tue Dec 20 11:06:41 EST 2016:DEBUG:Attempt 1 to execute request
    • Tue Dec 20 11:06:41 EST 2016:DEBUG:Sending request: POST /MicrosoftDynamicsAXAif60/WebSalesOrderRead/xppservice.svc HTTP/1.1
    • Tue Dec 20 11:06:41 EST 2016:DEBUG:Receiving response: HTTP/1.1 401 Unauthorized
    • Tue Dec 20 11:06:41 EST 2016:DEBUG:Connection can be kept alive indefinitely
    • Tue Dec 20 11:06:41 EST 2016:DEBUG:Target requested authentication
    • Tue Dec 20 11:06:41 EST 2016:DEBUG:Authorization challenge processed
    • Tue Dec 20 11:06:41 EST 2016:DEBUG:Authentication scope: NTLM @<website>:80
    • Tue Dec 20 11:06:41 EST 2016:INFO:<website>:80 requires Windows authentication
    • Tue Dec 20 11:06:41 EST 2016:DEBUG:Found credentials
    • Tue Dec 20 11:06:41 EST 2016:DEBUG:Attempt 2 to execute request 

    Event viewer on the server shows a similar error, "Object Server 01:  An error has occurred in the services framework.  Method: AifMessageInspector::AfterReceiveRequest.  Error: System.Security.SecurityException: The user name or password is incorrect."

    My first question would be what should be the correct user/pass, is it in terms of IIS or AX? We've tried multiple of combinations of course, but perplexed at this issue and led to believe it's something more. 

    Please, any insight would be appreciated.

    (

    Friday, December 23, 2016 4:20 PM

All replies

  • Hi Rasimh,

    Based on your description, it works under VS, and I assume your issue is related with SOAP UI configuration.

    Have you set Domain in SOAP UI, If you are authenticating NTLM, make sure to note the following in your configurations:

    ◦File > Preferences > HTTP Settings tab > uncheck Authenticate Preemptively preference

    ◦for NTLM v2 provide your username as "DOMAIN\USERNAME" or at least as "\USERNAME"

    I suggest you refer the link below for how to configure Authenticate Soap Requests in SoapUI step by step.

    # Authenticating SOAP Requests

    https://www.soapui.org/soap-and-wsdl/authenticating-soap-requests.html

    Best Regards,

    Edward

    Note: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you.
    Microsoft does not control these sites and has not tested any software or information found on these sites;
    Therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
    There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, December 26, 2016 6:57 AM