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.
REST API explorer authorization 'send as another user' sets instance session as another user - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • REST API explorer authorization 'send as another user' sets instance session as another user
KB0564452

REST API explorer authorization 'send as another user' sets instance session as another user


4121 Views Last updated : Jan 28, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

REST API Explorer authorization ‘send as another user’ sets instance session as another user

 

Objective
This article explains a current defect that affects session log in after running REST API Explorer. 
 
Versions affected
  • Fuji
  • Geneva

  

Procedure

Execute a REST call from the REST API Explorer page:

  1. Open Rest API explorer.
  2. Formulate JSON request.
  3. Select Retrieve a record (GET) (for example, from the table sys_user).
  4. In Authorization (under Request headers), select Send as another user.
  5. Provide credentials for another user (for example, AbelTuter).
  6. Click Send.

 


 

Problem

After running the REST call, the current user for that session changes to the user that executed the REST call (for example, Abel Tuter). However, this is not noticeable since the indicator at the top right of the page still shows the original user that originally logged in to the instance.

If you refresh the browser, for example by typing the URL of the instance on the same browser window, the user changes to the user who executed the REST call (for example, Abel Tuter).

 

 

Resolution


This is the standard behavior and the issue is caused by a limitation in the cookie mechanism.

Workaround

Immediately after executing the REST call, use the impersonate user feature to login as the original user that initiated the session.

 

Related links


  • REST API Explorer

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.