How to fix User/Identity - Account mapping

[AnithaMavurapu]

Hello Team,

We did imported Accounts  and Access from AD endpoints, imported user from ADP into Saviynt successfully. For User Account Correlation rule ADP source is not provided unique attribute which is in AD, in that case we did pulled the SamAccountName values from AD and tried updating into users systemusername using import file, but in this process we did missed updating Username field in the import file which is suppose to be  Reconciliation field for updating the systemusername, so it created additional user with invalid username and updated systemusername value of those created users. After all this we ran the AD import job with systemusername as  User Account Correlation rule and all the invalid username got created were mapped to AD accounts which are not right mapping where the actual valid users are not mapped. 

Could you please let us know if we can delete those invalid users that got created while updating the systemusername  using import file process with reconciliation field missed in the file.

And also could you please let us know how can we delete/remove mapping between these invalid users and Accounts in one short instead.

Thanks in advance......

Thanks

Anitha Mavurapu

[dgandhi]

You cannot delete the users from Saviynt. Mark those users as Inactive.

For removing the association with incorrect users, first mark these incorrect identity as Inactive then add the correct mapping in the  user account correlation rule and once this is done run the AD account import again. It should fix the and correct identity should be associated with the accounts.

Thanks

[AnithaMavurapu]

Thanks for your response Devang Gandhi. Yes as you mentioned we did marked these invalid/incorrect identities as Inactive already, but to add correct mapping in the user account correlation rule we do have have/see any common attribute. So to make that happen we planned to update one of the AD attribute value with Saviynt identity attribute value which is coming from ADP, for this update we have a import file with username, systemusername which got pulled from AD for respective active accounts that goes with corresponding username-identity, and CP65 value to trigger the update pending tasks. But when we imported this file we see the update tasks got created but not for the AD accounts which were mapped to incorrect identities around 200+ as of now. Now we are in process of fixing this user account mapping on these 200+ accounts. Sorry if it is not clear or confusing.

Is there any way that we can fix these incorrect users mapping without touching user account correlation rule, then import job and manually removing the accounts mapping from user UI?. Thanks in advance......

Thanks

Anitha Mavurapu