After cloning facing login issues

[Priyanka Nandip]

Yesterday i have  requested a clone from PROD to Non prod istance. Today i am facing login issues for non prod instance.

What i have to do now. Can anyone guide me to achieve this.

Thanks in advance.

[Sulabh Garg · Accepted solution]

Hello Priyanka,

Please see the below KB Article, It will help.

User unable to login after clone

CLONE - Frequently asked Questions (FAQ)

Why am I unable to log in after a clone?

This happens more often than you would think.

When cloning over an instance it brings the settings from production this can include SSO and login functionality that can cause you not to be able to login into the sub-production instance after the upgrade.

See KB0635905: The advantage of having a separate local login admin account when using SSO/LDAP.

This illustrates the benefits of always having a local account you can always log into, not only just for cloning.

To avoid this issue from happening for cloning you can do the following.

Method 1: Create a local admin user on the source instance.

1. Create a local admin user with a local password in your source instance
2. Clone over sub prod instance
3. Log in to instance using side_door.do with the username and password from step 1

Method 2: Create local admin user on target instance and include preserver.

1. Create a local admin user with a local password in your target instance
2. Create clone preserver for user (sys_user), user roles [sys_user_has_roles], and user groups [sys_user_grmember]
3. Clone over sub prod instance
4. Log in to instance using side_door.do with the username and password from step 1

Please Mark ✅ Correct/helpful, if applicable, Thanks!! 

Regards

Sulabh Garg

[George23]

The following video show you how to reset MFA after cloning.