In RSA Identity Governance & Lifecycle, duplicate entries are created when a user switches between two Identity Data Collectors multiple times
Originally Published: 2019-08-20
Last Modified: 2023-11-30
Article Number
Applies To
RSA Version/Condition: 7.0.2,7.1.0,7.1.1
Issue
The example below illustrates this issue.
- There are two IDCs: ActiveUsers and DeletedUsers. When a user is terminated, they are moved to the DeletedUsers data source. If they are reactivated, they are moved back to the ActiveUsers data source.
- Source Data for the ActiveUsers IDC:
- Source Data for the DeletedUsers IDC:
- After the first Collection, there is one entry for user Sunshine, Melody which is expected.
- User Sunshine, Melody is terminated and moved to the DeletedUsers data source:
- After the second collection, there is one entry for Sunshine, Melody as expected. This user is terminated:
- Next the user is reinstated by adding them back to the ActiveUsers data source and removing the entry from the DeletedUsers data source.
- After the third collection, there is one entry for user Sunshine, Melody showing the user is no longer terminated. This is as expected.
- The user is subsequently terminated again for the second time and the user record is moved to DeletedUsers:
- After the fourth collection, a second identity is created for user Sunshine, Melody. This behavior is not expected and is a defect.
Cause
Resolution
- RSA Identity Governance & Lifecycle 7.0.2 P15
- RSA Identity Governance & Lifecycle 7.1.0 P08
- RSA Identity Governance & Lifecycle 7.1.1 P03
