Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
A SOAP request with insufficient privileges yields a 200 response and empty response message instead of 403 error - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • A SOAP request with insufficient privileges yields a 200 response and empty response message instead of 403 error
KB0597534

A SOAP request with insufficient privileges yields a 200 response and empty response message instead of 403 error


2045 Views Last updated : Oct 16, 2023 public Copy Permalink
KB Summary by Now Assist

Description

A SOAP request with insufficient privileges yields a 200 response and empty response message instead of a 403 (Forbidden) error

Steps to Reproduce

  1. Create a new Outbound SOAP Message, using the WSDL for any table in the instance that contains records

  2. Create a user or use an existing user who does not have authorization to READ from this table.

  3. Edit the GetRecords function on the SOAP Message and set Basic Auth Profile as the unauthorized user.

  4. Edit the GetRecords function on the SOAP Message and remove any <!--Optional:--> items, so that the <sys:getRecords> element exists with empty data

  5. Execute the GetRecords function.

Note the 200 response code and empty response body.

 

 

Workaround

Using SOAP, there is no workaround available to obtain a 403 Forbidden error instead of the 200 response that is currently being returned. However, the equivalent REST endpoint will yield a 403 Forbidden error.


Related Problem: PRB711215

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.