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.
01/23/2023 08:43 AM
saviynt store this information in user_attributes table. so uniqueness will be maintained
01/24/2023 05:06 AM
If the old email has been updated and the email property of the user has been updated with a new value, will the old email still be in the user_attributes database?
We tested and saw that the old email of the user if no more attached to the user profile, can be assigned to a new user who fulfils the criteria
01/24/2023 01:01 PM
01/27/2023 02:04 AM
It is not working,
A new user with the same firstname and lastname gets assigned to an old email address which was once used by an old user.
Saviynt does not determine duplicity here because that email is no more in user database
01/27/2023 04:17 AM
01/30/2023 03:47 AM
@AshishDas I even have same kind of use case. Do let me know incase you get some clarification around the same (if any)