Best practice for moving multi SSO IDP from dev to test and prod

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-04-2022 11:17 PM
I am working on implementing multi SSO IDP and am curious to what is best practice when it comes to moving the IDP from dev to test and prod?
The IDP I am implementing have a test and prod environment.
When creating the IDP it is not saved in an updateset so I assume to move it I should use xml export and import. But is that the right way?
The next question I have is at what stage is the import table created when user provisioning is enabled ? I have modifed the transform map for the IDP I am working on and when I tried to export is and import on my PDI the import table was not created. And it was not created when I clicked on the link to the user provisioning transform map.
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-05-2022 12:21 AM
Hi
it is not recommended to move the configurations to the next instance, as each IDP connection is highly individual for both partner systems
Instead document all steps required to configure and establish the connection.
Kind regards
Maik

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-05-2022 12:31 AM
How would you mange the situation that users are cloned from prod to dev and test. Dev/test users should not use the prod IDP but the dev/test IDP ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-05-2022 01:55 AM
Hi
the following two pages will answer your questions:
- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0657100
- https://docs.servicenow.com/en-US/bundle/sandiego-platform-administration/page/integrate/saml/task/t...
Kind regards
Maik