Issue with autoincrement in account name rule for AD Connector

[reshma_sonawane]

Hi Team,

We have configured account name rule with advance config for AD connection with auto increment to handle duplicate accounts.

With this we found that, account name rule is working fine with autoincrement when there is an duplicate. But, for existing AD account and if saviynt triggers update account task based on attribute update, it is incrementing CN value for existing CN rather that keeping it as is. Please find example below.

Accountrulename format:

CN= FN LN, OU=....###CN= FN LN1, OU=....###CN= FN LN2, OU=....###CN= FN LN3, OU=....###CN= FN LN4, OU=....

1.User with DN=FN LN,OU=users,... created in AD.

2. Update account task is triggered for attribute update(Say department number is updated for user) for above account

3. Above Accounts DN gets changed to DN=FN LN1,OU=users,... and department number is updated in AD

Expected result: It should just update department number in AD  without any change in DN

Could you please let us know why is it incrementing DN by 1 for existing account?

[nimitdave]

Can you confirm if you are using moveUsertoOU in updateaccountjson.  As account name rule will only be evaluated in move user to new OU scenario in update account.

Also check if any other user with same CN is not present the target new OU.

[reshma_sonawane]

@nimitdave We have moveUsertoOU in updateaccountjson. When there is OU movement and update task is triggered, it is working as expected however when there are any other updates, even then it is evaluating accountnamerule and incrementing CN of existing user by 1

[nimitdave]

And no user exist with same CN in the new OU?

[reshma_sonawane]

@nimitdave Yes. No issue found with OU movement. Issue exists  when other attribute are updated.