Can't Add New Clone Target - Authentication Fails

[Geoffrey_Bishop]

This may help someone...

If you are unable to add a new Instance via Filter Navigator - Clone - Clone Targets (table: "instance"),

Are you are getting the following error messages:

     "Invalid username or password"
     "Invalid Insert"
     "To clone to an instance, you must have admin privileges on the target instance."

Try the following.  On the target instance, temporarily disable Multi-factor authentication via Filter Navigator - Multi-Factor Authentication - Properties (table "sys_properties", record "glide.authenticate.multifactor").  Then try adding the Clone Target again.  Then re-enable MFA on the target instance.

Screenshots:

[Suzanne Coffman]

Do you have to leave MFA off in the non-prod instance until after the clone has been applied to the instance?

[SeanM1]

Thank you, this got me out of a bind.

[Shawn Roach]

Adding another thank you for this post!

[JStockel]

Thank you so much! This really had me pissed off for a whole day trying to get around it, resetting passwords and all...
Should be an info note in the whole Clone process, or in the ServiceNow documentation for cloning.

[Roy Barclay]

I was running into this issue and took all of the above steps above, but the errors persisted. 

Fix that worked:
Navigate to Multi-Factor Authentication > User Multi-factor Setup
Deleted "User Multifactor Authentication" Record for target account record

This resolved my issue and I was able to create the Clone Target

[Luiz Lucena]

Hi @Geoffrey_Bishop 

The account you are trying to use must exist in the target instance, username and password. 

We use SSO here and the company account I use to login to all our instances doesn't work when doing the clone request. 

For these situations I have a local account in all instances and when requesting the clone, we need to pass that local credentials to authenticate in the target instance from PRD.
Having a local account also helps as a backup in case SSO is down.

Hope that helps.