AnsweredAssumed Answered

Authentication problem using Call a Web Service action

Question asked by barryc Champion on Jun 9, 2015
Latest reply on Mar 9, 2017 by barryc

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.