HTTP 401 Unauthorized error when requesting a clone using the new Clone Admin Console

[nataliyee]

Has anyone experienced an HTTP 401 Unauthorized error when requesting a clone using the new Clone Admin Console?

I'm using OAuth authentication and can request a clone to TEST without any issues, but DEV returns a 401 error. I’ve tried using the Reset OAuth option but nothing happens when I click it so I’m unable to complete the reauthorization process

[Hemanth M]

Hi @nataliyee ,

I believe you have already tried these, if this is still an issue, please open a Now Support ticket with ServiceNow.

OAuth 2.0 authentication for clone targets -https://www.servicenow.com/docs/r/platform-administratio... 

Set up OAuth authentication for a clone target - https://www.servicenow.com/docs/r/platform-administ... 

[VJ_Srivastava]

Hello @nataliyee,

From an infrastructure architecture standpoint, encountering a 401 Unauthorized on DEV while TEST operates flawlessly is a strong indicator of configuration drift between your lower environments.

The Clone Admin Console relies on a tightly synchronized OAuth Application Registry between the source and target instances. If your DEV instance recently underwent a sub-production patch, or if a previous clone partially overwrote the OAuth application records without preserving them, the Client ID and Secret expected by your source instance will no longer match DEV.

You must inspect the Application Registry (oauth_entity table) on the DEV instance. Ensure that the inbound clone application profile matches the exact credentials stored on your source instance. If the integration profile on DEV is inactive or out of sync, the token exchange will universally fail with a 401, regardless of how many times you attempt to reset it from the source.

[NehaG8791370651]

Hi @nataliyee,

The unresponsive "Reset OAuth" button is almost always caused by a silent browser popup blocker preventing the target instance's login window from launching. Because the UI action fails to open the authorization window, the stale token remains stuck, resulting in the persistent 401 error.

Here is the backend technical workaround to force a reauthorization:

• Bypass the UI: Type oauth_credential.list in your application navigator to access the raw OAuth credentials table on your source instance.

• Flush the Stale Token: Filter the list for the credential associated with your DEV instance (this is typically tied to the Clone Automation or Clone Admin Console profile) and permanently delete the record.

• Verify Target Credentials: Ensure the admin account you are using to authenticate on the DEV side is active, not locked out, and that the password has not expired.

• Reauthenticate: Return to the Clone Admin Console, completely disable your browser's popup blocker, and attempt to set up the clone again. The system will detect the missing token and instantly force a fresh OAuth login prompt.