Cannot login in development

[Karen Chan]

Anyone can help me? I can't enter development after cloning. It keeps saying that my account and password are wrong, and so do other administrators, but ordinary users can log in normally.

[Community Alums]

Hi @Karen Chan ,

The sys_user records need to be preserved and excluded to retain the local records in the lower instance table as they are. If this solution is implemented, it is recommended to also preserve the sys_user_has_role ,sys_user_role and sys_user_group tables along with the sys_user table to maintain the relationships across all the users and their roles.

Also, when the sys_user records that are present in Production but not in dev, can result in records where that user record is required to have empty references. So please use this option only if you really need to preserve the records in sys_user table as is.

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.

[Karen Chan]

Sorry, the  KB0635905: The advantage of having a separate local login admin account when using SSO/LDAP show 'Your role does not grant you access to this article. Please use Search to find related content.'

[Sandeep Rajput]

@Karen Chan Looks like records from your sys_user table have also been cloned along with the instance. I am assuming you cloned your production instance on development, if this assumption is correct, could you please try login using your production instance user name and password and see if it works.

[Karen Chan]

Yes, sys_user table have also been cloned along with the instance. But my account and other one admin account cannot login to development, this confuses me.