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

nataliyee
Tera Contributor

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


7 REPLIES 7

Hemanth M
Tera Sage

Hi @nataliyee ,

 

Go to Clone Instances from the Configuration tab and make sure username and password is correct for the Dev instance (which will be pulled from the dev instance) or do a password reset in dev for this account, update the password here and try the clone request again!

HemanthM_0-1792689412777.png

 

you can also check this - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3140805

 

Hope it helps!

Thanks for your suggestion. I'm using OAuth, so there isn't a username or password to update under Clone instances. 

Tanushree Maiti
Tera Patron

Hi @nataliyee 

 

Refer KB: KB0853086 User may encounter MFA when raising a clone request despite disabling it in sys_user table 

 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0715621

Clone target authentication fails with "Invalid username or password"

Due to recent changes with security and the enforcement related to BasicAuth changes, we have seen an increase in authentication failure related to those changes

1) For clone requests we recommend to have a local account with identity type field set to machine and this will automatically checks the "Web Service Access Only" option.

  1. Open any user record from the sys_user table.
  2. Right-click the form header and select Configure → Form Layout.
  3. Move the Identity Type field from the Available column to the Selected column.
  4. Click Save.
  5. Set the Identity Type field value to Machine.

Note: When the Identity Type field is set to Machine, the user will not be able to log in to the instance. As a best practice, create a separate account specifically for clone authentication purposes.

Thanks for your suggestion. I'm using OAuth, not Basic Auth. I forgot to mention that