Best Practices to Purge Sources in Production – Identity Security Cloud

Identity Security Cloud (ISC) ISC Discussion and Questions
1

:bangbang: Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.

Please consider addressing the following when creating your topic:

Best Practices to Purge Sources in Production – Identity Security Cloud without impacting existing environments.

2

Remove any access profiles and Roles associated with the source. Ensure that the source owner does not have an account in that application; if they do, reassign source ownership to another identity that has no accounts on that source. After that, perform a reset of accounts and a reset of entitlements. Once these cleanup steps are complete, you can safely delete the source.

3

Hey @narayanag ,

Adding on to Chaitanya, This is how we keep it in practice:-

  1. Remove the source name from any identityprofile and transforms(If applicable).

  2. Reset accounts and entitlements.

  3. Disable and delete access profiles and roles.

4

To safely purge sources in SailPoint Identity Security Cloud production, first remove all dependencies by unlinking entitlements, removing access profiles from roles, and disabling app access. Use the Source Reset API to remove accounts, then remove provisioning features. Finally, delete the source and confirm no authentication pass-through exists.

6

@AsGoyal,

@ Aayush Goyal There are many transforms in the production tenant, but we do not have direct access to the tenant and can interact with it only via Postman. How can we verify whether the source name exists in all transforms?

7

@narayanag,

You can use this API to get all the transforms