In this session, we will explore the process of migrating an authoritative source within SailPoint Identity Security Cloud. We will discuss the key steps and best practices for migrating data from an existing authoritative source, ensuring seamless integration, data consistency, and security.
Migrating an Authoritative Source Compass Article:
Scripts used in the video:
Get-MigrationComparison.ps1 (6.4 KB) - Compares Identity Attributes
Preview-Users.ps1 (4.3 KB) - Refreshes the Preview API for a given set of users
Q: What version of PowerShell is this compatible with?
A: 6.00+ (Tested with 7.3.6)
Dependency on -ResponseHeaderVariable
Install PowerShell 7.5
Thank you for the demo.
Is it safe to change the profile priority before validating?
It could trigger an attribute synchronization with incorrect values, couldn’t it?
If you repeat the steps to transfer over the old Identity Profile mappings to the new Identity Profile, the transforms should calculate to the same values. Then once the comparison is done the updates to the profile can be made. That said, if there are any differences, those may be synced and should be taken into consideration.
We are about to do this ourselves.
The approach that I’ve suggested is that for each identity attribute make a dummy attribute (we have 150 - don’t ask).
On the existing profile you point the dummy attributes to the new source, but on the new profile, the dummy attributes are left blank.
Once you have 100% data match on the existing profile, you can promote the new profile without any fear.
I personally would not write any transforms that reference the old source, because you won’t be able to delete it until after those transforms have been deleted. The main four attributes should be tested to exist well before ingesting into PROD.
Anyway, I’ve got 100+ transforms to write. Wish me luck.
