We integrated AD ,Google & Exchange in our Project.
In Exchange it has current Email ID as Primary SMTP in Exchange. All previous Email IDs stored as secondary smtp addresses.
Currently Saviynt is only checking existing User Email IDs of users in Email Generation Rule. If it present already it creates with next integer value. But this value may present in AD/Exchange as Alias(smtp) address.
E.g: In this case if another Ram Kumar joining and lets say firstname.lastname@example.org and email@example.com already present in Saviynt.Then it will create next email id as firstname.lastname@example.org which is already present in exchange as smtp for another user.
Also we pulling all proxyAddresses to one of the attribute in Saviynt using AD user Import job as below. As exchange data hosted in AD only.
But we want to understand how we will verify all these proxy addresses before creating a new Email ID for a new Joiner.
How it implemented for other Clients to avoid this issue.
Email generation rule checks the uniqueness of generated email in below:
1. Existing Users email irrespective of status.
2. Account Name of all accounts in saviynt irrespective of status
3. Data in User_Attributes table. User_attribute table is exposed in inlinee preprocessor. So emails from any target which is not mapped to account name can be catured in this table and then email generation rule will check uniqueness on this data also.
Can you help us to provide some format how we can map Email from every target to User_attributes table and use inline preprocessor query to validate it before generating Email ID.
Currently we configured Email Generation rule as below:
If this email already present then we incrementing with next integer value.
But it only checking the Email ID already exist or not. if it present creates with next number. But not checking User_Attributes.email attribute while generating new email id.
Is there any other configuration we need to do Email Generation rule to check it? Is it a bug if it not doing so?