Click HERE to see how Saviynt Intelligence is transforming the industry. |
02/23/2023 01:54 PM
At the beginning of the project, the client provided the wrong unique identifier for users imported from the HR system. After the users were imported, their AD accounts were correlated (user.systemusername = account.name) with the users.
Later the client provide a different HR source field to store in user.systemusername, and Saviynt needs to correlate AD accounts to the users with the new systemusername.
To do this, I made all existing users inactive and appended a string to their systemusername (i.e. 123456.OLD). Then I ran the user import job, with the systemusername sourced from the the new field.
Then I ran the AD account import job. On completion, the AD accounts are not associated with the new users. They are still associated with the old users.
Steps following:
1. Update AD endpoint, removing the user correlation rule, and then running the AD account import job.
2. Update AD endpoint, adding back the user correlation rule, and then running the AD account import job.
After these steps the account are still associated with the old User.
What can I do to associate the AD accounts with the new users?
02/23/2023 02:35 PM - edited 02/23/2023 02:40 PM
02/26/2023 05:21 PM
Overwriting user assignment seems broken in v 23.2
Here's how I tested it:
Since the following did not change the user assigned. I uploaded the account, and selected 'Import From Job'. And it still didn't work.
02/26/2023 08:49 PM
Yes not working for me too