Workaround to remove duplicate identities resulted to mapping of account to a terminated account instead of the active one
2 years ago
Originally Published: 2017-05-01
Article Number
000067682
Applies To
RSA Product Set: Identity Governance and Lifecycle
RSA Version/Condition: All versions
 
Issue
For instance, duplicate Identities were accidentally collected within your system (same UserID) which caused a series of issues i.e. one being authentication login.

And what you did to resolve this was:
1. To get the original IDC (first introduced prior to the duplicate) to return zero rows, and have its Users terminate so there would be only one of the two duplicates active in the system.
2. The second IDC created would instead be the only one returning the active User.

The issue this caused is that the system maintains mapping to the terminated/disabled account instead of the active one.

Is this proper behavior, or should the system ideally know to move mapping to the active User?
Resolution
In this scenario, the mapping of an account to a deleted user is working as designed.
This is a required functionality from other Customers as this is a security hole.

The problem that can occur is this: 
i.e.  A user can be terminated/deleted, but if they still have access to the account, then if someone were to get access as that 'user', they would have access to the privileges to the account as well.

There are other scenarios where users were subsequently rehired by companies in a different role.
If this mapping is not identified then a returning employee may have privileges that their new role does not require.