Error in soap message

saahilkumar
Tera Contributor

Hi All

I get an error while generating a SOAP message i.e

Unable to load WSDL: java.lang.RuntimeException: org.apache.commons.httpclient.HttpException: Unable to retrieve XML, HTTP status code: 401:org.apache.commons.httpclient.HttpException: Unable to retrieve XML, HTTP status code: 401

How to address this error

Thanks in advance

find_real_file.png

1 ACCEPTED SOLUTION

Pradeep Sharma
ServiceNow Employee
ServiceNow Employee

Hello Saahil,



An HTTP 401 response means that your request is unauthorized. Please create a user account to authenticate with( soap roles assigned), and select 'use basic auth'.


http://wiki.servicenow.com/index.php?title=Base_System_Roles


View solution in original post

12 REPLIES 12

Hi Ankur



Thanks for the revert


How can the roles be added to the user.



Thanks


Saahil


Hi Saahil,



First try without giving any roles. Whether that works or not.


If it works then it should be good.



Regards


Ankur


Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader

JV2
Tera Expert

Hi,



I'm not sure if this questions should be considered answered yet. The basic authentication profile required on the SOAP message definition is not a regular ServiceNow user (sys_user). It's a Authentication Configuration. see image below:



                            find_real_file.png



If you define a user in this form (select the "New" button), that user is not a regular user, so no roles can be assigned to it



These other threads are referring to the same issue, and are set as not answered:


https://community.servicenow.com/message/1043932#1043932


Generation soap message, Please help



So, has anyone really found a solution for this issue?



For the records, in Geneva, all you needed was a regular ServiceNow user ID and password. In fact, if you browse the XML of the SOAP message defined in Helsinki, the field "use basic authentication" is still there, and when this one was set to true in Geneva, it displayed the user/pwd fields to populate with the regular SN user information. So, it looks like Helsinki moved (or tried to) to a more controlled user authentication approach; but there is something not properly documented yet... Any thoughts?



                            find_real_file.png