I have two web apps running on the same box / domain. Each of them uses ADFS authentication however they have also been extended to include windows authentication running on port 8443. As far as I can tell, both are set up exactly the same way.
In web app 1 we quickly realised that web service calls had to be made via the :8443 windows auth URL. No problems there. All is good. Web service calls execute just fine.
However, web service calls attempted via the Call a Web Service action in web app 2 behave strangely. Firstly I can browse to the web service definition without issue:
e.g. https://WEBURL2:8443/_vti_bin/lists.asmx pulls up the list of methods
Attempting to pull up the list of methods in the call a webservice action always gives an unauthorised error (my credential - both ADFS and domain\accountname - is site collection admin)
One strange thing I have noticed that may be a red herring, when I navigate to an imported web service call that already contains the method etc. and use the run now option the username field seems to be pre-populated with a random piece of HTML!
Replacing the username and password here with something valid still always yields - Request failed with status: Unauthorized.
Anyone have any thoughts? I am of course open to ideas that something is not quite the same between the two web apps.
Solved! Go to Solution.
Regarding the Call web service 401 unauthorised issue, have you tried opening the same web service in the browser from the server itself ? i.e you need to RDP into the server and test, does it give the same Unauthorized error?
I would check the AAM settings for both Web Apps and see if there are any differences?
Please see this MSDN link about the loop back and see if it will apply to you: https://support.microsoft.com/ja-jp/kb/896861/en-us
Regarding the Call web service 401 unauthorised issue, have you tried opening the same web service in the browser from the server itself ? i.e you need to RDP into the server and test, does it give the same Unauthorized error? I would check the AAM settings for both Web Apps and see if there are any differences? Please see this MSDN link about the loop back and see if it will apply to you: https://support.microsoft.com/ja-jp/kb/896861/en-us
Yes I have tried opening the web service on the server. The behaviour is exactly the same as on the desktop. I can browse to the web service definition but any time I try to access it via workflow I get unauthorised.
I cannot see any difference in the AAM settings between the two web apps but I'm sure there must be something subtle there!
i believe the Auth is different between WebApp1 and WebApp2. Would you be able to check the ULS log and see the stack trace when you get the Unauthorized error? it might shed a light which API is called during the authentication.
Just as a side note, would Web request action give you the same error? and also does the Web service Studio tool https://webservicestudio.codeplex.com/ would allow you to connect successfuly ?
Bump with same issue.
I have confirm that the account used to view the Nintex web service [Web URL]/_vit_bin/NintexWorkflow/workflow.asmx does work. On our development server, the SharePoint web application is on http protocol, but on production it is on https.
Hi Rhia, sorry I cannot say...I never did find a solution for this and ultimately it was left unresolved. If a registry key was the issue I'm not sure why one web app would work properly and not the other?