Symptom
You need to automatically delete users from IAS if their corresponding user in Success Factors changed to "INACTIVE" state.
Environment
- SAP Identity Authentication Services
- SAP Identity Provisioning Services
- SAP Success Factors
Reproducing the Issue
Cause
Users are not automatically removed because they were not provisioned via IPS provisioning job after adding property "ips.delete.existedbefore.entities = true" in target system.
Resolution
The steps below is an example to read and create the inactive users in IAS, and delete the inactive users by adjusting property sf.user.filter. The original value of sf.user.filter is only an example. Please adapt the value of sf.user.filter base on your scenario.
Please note that the inactive users will be created in IAS after step 3, and maybe activation email will be sent to these users (depends on the transformation). Please understand the impact of the step 3 and decide whether to use this way.
- Make sure you have the property "ips.delete.existedbefore.entities = true" in target system;
- Then, in the source system, change the property sf.user.filter from status eq 'active' to status in 'active','inactive';
- Run the READ job;
- After the job finishes, change back the property in the SOURCE system from status in 'active','inactive' to status eq 'active';
- Run another READ job and the 'inactive' users should be automatically deleted from now on when running the IPS provisioning jobs.
Please note: The deletion activity is executed only in that case when there are no failed entities for the source system transformation. This feature was added by the IPS developers to avoid any errors.
See Also
Keywords
IPS, automatically remove, SF, inactive, no longer part of the company, Identity Provisioning Services, Success Factors, Identity Authentication Services, IAS, ips.delete.existedbefore.entities, status eq 'active' , KBA , successfactors , BC-IAM-IPS , Identity Provisioning Service (IPS) , How To