#SharePoint #Call Web Service I am trying to invoke SharePoint Web Services by m

sikhivahans over 8 years ago

#SharePoint #Call Web Service I am trying to invoke SharePoint Web Services by making use of Call Web Service Smart Service. Even after providing the correct WSDL, username, password and domain (I have tried it with 3 different values namely NTML, IAM and blank value (null)). The error we are experiencing at the moment is as follows (Attached the screen print):

The WSDL requires authentication. Please provide valid credentials (APNX-1-4045-006)

I have seen previous posts on the same lines and as per my understanding, they are not yet or partially resolved. I saw some posts talking about the domain and their compatibility with Appian. Would someone here please be able to guide in a right direction?

Appian 16.1 and SharePoint 2013 are the environments being used.

Thanks in advance.

Discussion posts and replies are publicly visible

0 mathanap over 8 years ago

Can you try calling the same wsdl using the SOAPUI or other tools and check whether you are observing the same error pattern. So we can sort out the compatibility issue.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Stefan Helzle
A Score Level 3
over 8 years ago

Hm ... last time I integrated with SP the admins created a separate login domain restricted to the Appian system and set it to basic authentication and SSL. But that may not be an option for you.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sikhivahans over 8 years ago

I would like to add one more confirmation here, the same wsdl, username, password and domain(IAM) is working perfectly with Soap UI and I am able to see all the methods present in it.

@stefanh If you don't mind would you please be able to expand on what you have said?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Stefan Helzle
A Score Level 3
over 8 years ago

I did this some years ago and used the REST interface to read and write data to lists. This was with SP 2007 I think. We where not able to get the NTLM/AD authentication working and the only alternative on SP side was to activate basic auth. But to separate access for normal users from the Appian connection we created another sort of container in SP just for that. I am no SP specialist, this is just what I heard from the admin team. But that works without any problems.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sean Kim
Appian Employee
over 8 years ago

Hello! Is there any error in the server.log when you try to invoke the wsdl? If you do a network capture, do you see any relevant HTTP codes?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sikhivahans over 8 years ago

@sean.kim Please find attached the logs.
logs.txt
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sikhivahans over 8 years ago

@stefanh Thanks for your suggestions and sharing your experience.

@sean.kim Would you or some one from Appian Product Team be able to justify why Appian isn't able to consume the SharePoint WSDL? It would be really grateful if you or some one from the Product Team could let us know where the problem lies - that is, is it with our configurations/infrastructure or is it a limitation within Appian?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sean Kim
Appian Employee
over 8 years ago

From our Documentation:

"NOTE: Some SharePoint SOAP Web Services are not compatible with the Appian Call Web Service framework. We recommend the SharePoint RESTful Web Services and the a!shp* connector functions instead."

- forum.appian.com/.../Appian_for_SharePoint_2013.html

So I believe this is a framework limitation but I can follow up with our product team. I know RESTful is more robustly supported with Sharepoint.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sikhivahans over 8 years ago

@sean.kim Yep we are aware of that but we would love to hear what's going wrong here.

In-fact our RESTful implementation was quite smooth but we would like to hear from you re the nature of the issue we are experiencing with SOAP Web Services. We are looking forward to make any corrections in the implementation just in case if we have done any mistakes from our side, and also we would like to see what Appian comes back with regards to this. I saw some forum posts unanswered or partially answered on this issue and it would be grateful if we can come to a decent conclusion.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Stefan Helzle
A Score Level 3
over 8 years ago

I also tried to consume the SP WSDL files. The problem is that the datastructures are mostly defined as "ANY" and "MULTIPLE" and Appian is not able to map that to real datatypes.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel