Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Account to account correlation - Preventing Duplicate Accounts in Security Systems

Murmur
Regular Contributor II
Regular Contributor II

Hi everyone,

We are currently facing an issue where users receive additional accounts in our AD security system. The problem arises due to a change in our account naming scheme. Previously, accounts were named using the format firstname.lastname, but now we are using the employeeID instead (example below).

Does anyone have an idea on how we can prevent Saviynt from creating additional accounts if an account already exists in the Security System?

Thanks in advance, and have a great day! 😊

Example

User: First.Last@mycompany.com (eID_123)

Existing AD account: first.last

With our Birthright Technical Rule we, create a new AD Account: eID_123

Murmur_0-1704965730183.png

 

2 REPLIES 2

rushikeshvartak
All-Star
All-Star

What is account name rule configured currently. You may re import all account using employee id to avoid this issue


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Manu269
All-Star
All-Star

Update the user account coorelation rule with new logic and then perform import.

Post that try validating the create account operations

Regards
Manish Kumar
If the response answered your query, please Accept As Solution and Kudos
.