Authentication issue after cloning

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2014 03:09 AM
hello,
When cloning from a SSO Prod system to a non prod that uses local passwords,authentication is not working on non-prod environment even though sys_user is preserved in nonprod environment.we have raised a ticket with service now support but from past one week,we are not getting any root cause from them.Did anyone faced similar issues in their environment?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2014 12:18 PM
Take a look at what we have developed at Perspectium. ServiceNow admin's can use Replicator for ServiceNow to replicate and synchronize your production data with other ServiceNow instances. We can help you reduce the frequency and eliminate the need to clone.
www.perspectium.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2014 03:59 PM
Hi mishra2007,
I have experienced something similar during a cloning process. You will need to carry out a few checks.
- You will need to disable SSO for the non-prod environment.
- Passwords will not be stored locally within ServiceNow on the non-prod environment after the clone, this means new passwords will need to be created for each user.
- Users should then be able to login using the locally created passwords.
Let me know how that works for you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2023 01:42 PM
This video shows how to fix mfa after cloning.