Integration error for Sharepoint SOAP service and WSDL

sandeepr373

A Score Level 1

over 6 years ago

Hi All,

I am trying to access Sharepoint service (both SOAP and WSDL) through Integration but i am getting below error:

error: IntegrationError

title: "Unsupported authentication"

message: "This request requires Negotiate authentication which is not supported by Appian" detail: "HTTP/1.1 401 Unauthorized"

but when i tried both services via chrome app Postman, its working fine. this wsdl or SOAP service dont require credential to acess but in appian its saying unsupported authentication.

does appian support accessing of Sharepoint services (Both SOAP and WSDL)?

Discussion posts and replies are publicly visible

0 sandeepr373
A Score Level 1
over 6 years ago

also getting below error:
error-result-guidance
This request requires Negotiate authentication which is not supported by Appian
HTTP/1.1 401 Unauthorized

Next Steps

Review the external system’’s documentation to see if alternate methods of authentication are available
For internal systems, contact an administrator to see if alternate methods of authentication are available
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 aloks0189
Certified Lead Developer
over 6 years ago

Hi sandeepr373 a quick question here,

What do you mean by SOAP service and WSDL because as far I know, WSDL is a definition file which describes the SOAP service in the form of XML
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sandeepr373
A Score Level 1
over 6 years ago in reply to aloks0189

Hi Alok,

Yes you are correct. Actually i have 2 urls, one is wsdl and another one is with .asmx extension which is basically returns list of operation when we test it on IE. i tested that wsdl in appian but its giving above error which i mentioned.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 aloks0189
Certified Lead Developer
over 6 years ago in reply to sandeepr373

Hi Sandeep, by any chance did you try using Call Web Service smart Service (OOTB). It's pretty much flexible when we want to deal with SOAP services. And I believe this smart Service will do your job.

Set the authentication to no authentication in case your service do not expects authentication.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel
0 sandeepr373
A Score Level 1
over 6 years ago in reply to aloks0189

Hi Alok,

thanks for reply.
i tried using Call web service also, but no luck. it showing error "The WSDL requires authentication. Please provide valid credentials (APNX-1-4045-006)". but there is no authentication required for accessing wsdl.

Regards,
sandeep
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 aloks0189
Certified Lead Developer
over 6 years ago in reply to sandeepr373

You can try something like:

Create a third party credential in Appian where userid and password will be a valid user of Appian and use this username and password as user id and password for this smart service. And try checking whether it's getting invoked or not.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 manojt
Certified Associate Developer
over 5 years ago in reply to sandeepr373

Hi Sandeepr373,

i faced same issue when i tried to consume BP url in appian where i kept getting this "HTTP/1.1 401 Unauthorized" error which indirectly means its authentication issue.
So it worked for me in soap ui but not in appian .later we found that the issue was with Key " Authorization" where it was case sensitive where from appian it comes in Small letter.
So pelase check this in postman/Soap UI to cross verify it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel