Hello everyone,
I need to develop a reactivation use case in SailPoint Non-Employee Risk Management (NERM), and I would like to know whether anyone has implemented a similar scenario.
Currently, SuccessFactors (SSFF) is the authoritative source for internal employees. When an employee leaves the company, their identity in SailPoint Identity Security Cloud (ISC) remains in a Terminated state.
The new NERM use case should cover the following scenario:
- The person previously worked as an internal employee.
- Their identity already exists in ISC and is currently in a
Terminatedstate. - The same person must later be onboarded as a non-employee through NERM.
- The user who launches the reactivation use case would enter the person’s email address.
- From NERM, an API call should be made to verify whether the identity already exists in ISC.
- The existing identity identifier would be retrieved from that API response.
- A NERM account would then be created and correlated to that same identity.
- Finally, the email address and other attributes would need to be updated so that the identity represents a non-employee.
The main challenge is that the authoritative source for internal employees uses a different identity profile from the identity profile configured for NERM accounts.
Because of this, I am not sure how to assign the non-employee attribute values to the same existing identity, or how to manage the attribute updates while the identity remains associated with the internal employee identity profile.
Has anyone implemented a similar use case?
Is it possible to correlate the new NERM account to the existing identity and update its attributes with the non-employee values, even though the identity was originally created from a different authoritative source and identity profile?
What approach, configuration, or mechanism would you recommend for this scenario?
Thank you in advance.