01/23/2023 01:33 AM - last edited on 01/23/2023 08:23 AM by Dave
Is there a way to restrict a new user from getting assigned to an email address that was initially assigned to an old user?
Use Case : We have a requirement that when the company of the user (say John Doe) changes, their email address is updated. That is, if user was in company ABC initially then their email was email@example.com, but after their company change to XYZ, their new email would be firstname.lastname@example.org, which would reflect in the email attribute of the user.
However, since email@example.com is no more in the Saviynt database anymore, as it was replaced with firstname.lastname@example.org, hence the duplicity check does not work here and the new user with same name is assigned email@example.com , which we do not want.
Any workaround on how to achieve this? Does saviynt check the secondary email attribute of users too while checking for duplicate email addresses while generating email addresses?
Let me know if any further explanation is needed.