Key to successful cloning of instances with SSO?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi everyone,
I need your advice, as I struggle with cloning Full PROD over SSO/MFA enabled TEST instance for my customer.
I've read a lot of materials, KB articles and official documentation, but it still does not manage to retain multi-factor authentication working on the target, resulting in such messages:
I used the following documentation as reference:
- Data preservation on cloning target instances
- Clone an instance with a SAML integration
- Checklist before cloning an instance with Digest / SSO / SAML / Multi SSO Integration to prevent den...
- Users not able to login in cloned target instance using Multi Factor Authentication (MFA) - Support ...
- Exclude a table from cloning
Based on these, I have modified my Profile's list of Preserves and Excludes (I can paste both in a comment later). However, I do not know if this list if comprehensive. I also could not find any recommendation regarding the cleanup scripts, so I included them all.
In any case, I do have a number of questions:
- Should I preserve sys_user and related table - partially (maybe keep an admin user) or all?
- What tables should I include as Preserves and Excludes?
- What clean-up scripts shall I include in the profile?
- Do you have an experience with cloning over a SSO enabled instance? What was your approach?
Thank you all in advance for the support!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
36m ago - last edited 33m ago
I have never had an issue with this. It looks like the table for multi-factor are already setup in the preserve data. If you are using clone profiles you may want to make sure they are still part of the preservations.