SOAP Message HTTP/1.1 401 Unauthorized Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-14-2015 07:00 AM
Hi, We are trying to connect SOAP Message created in Service Now. We have downloaded certificate from the wsdl url and registered in our windows server from where we are making the call. This SOAP Message is defined as Basic Authorization with userid and password. It works fine using SoapUI IDE and able to create ticket in service now dev.
This requirement is to integrate IBM Bus flow to Service Now (currently testing in DEV instance). On connection we are getting error HTTP/1.1 401 Unauthorized.
Is there properties need to be set? Completely new to ServiceNow products.
Thanks for your help.
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-14-2015 10:30 AM
Hi,
I am integrating another product and are also getting the same errors, and I also quite new to SN. I am also doing Basic Authentication to WSDL SOAP in imported Update Set.
In the latest SN version Fuji it seems like the security settings have been ramped up. This is what I have tried so far based ;
1. Elevated admin for my admin account (top left corner keypad)
2. Changed the High Security settings to disabled;
- Enforce strict security on incoming SOAP requests
- Require authorization for incoming WSDL requests
3. Set the ACL for WSDLProcessor to Inactive
4. Changed the Require basic authentication for incoming SOAP requests in Web Service Properties to No
5. Changed System Properties > Security > Security Manager default behavior in absence of any ACLs on a table to
- Allow Access
6, Still isn't working
I know it doesn't help telling you what didn't work for me, but I figured I share what I had tried so far...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-14-2015 05:17 PM
Did you give the soap roles to the userid which is being used for basic authentication in ServiceNow?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-15-2015 12:49 AM
Hi Guys,
I did give the user the appropriate roles, and after that did some more testing and researching. I was still getting the Forbidden error message;
The HTTP request was forbidden with client authentication scheme 'Basic'. The remote server returned an error: (403) Forbidden.
I finally found an obscure little comment in the ServiceNow documentation about Applications and security, and this is new in the Fuji version! It specifically mentioned the forbidden errors in case not configured properly. This is the page: Application Access Settings - ServiceNow Wiki. There seems to have been a lot of added security in Fuji, but the defaults seem in a lot of cases to not be backwards compatible with the configuration from previous version.
Basically, each table in an imported Application have some default security settings, namely "Can read" and "Allow to be accessed via Web Services". I first thought the second one was not enabled, but for all my tables it was. However, there are two other settings that my application needs enabled; "Can create" and "Can update". Once i enabled those for my tables the integration worked. Please let the community know if this works for you too, Robi?
I am all for added security, but it was really difficult to find this information for some reason. I hope the above helps if so that others with the same issues finds this article easily...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-15-2015 09:09 AM
Hi Akhilesh, yes i have given user rights as described below
http://wiki.servicenow.com/index.php?title=SOAP_Web_Service#Enforcing_Strict_Security
Hi Richard,
It works and insert incident records using SOAPui tool with basic authentication. It has to be something our IBM Bus flow missing something.