Use Case
Achieve Email uniqueness check during email generation against existing proxy addresses/other attributes mentioned apart from the email attribute field.
A common use case to to have a lookup table before generating email so that any other unique check can happen and generate the email accordingly.
Pre-requisites
Target system ( i.e AD or Azure AD or Exchange ) is connected already with Saviynt.
We just need to import proxyAddresses ( user import ) extra attribute, process them and fetch Primary SMTP and save them in the data column in the userAttributes Table.
Applicable Version(s)
EIC v21+
Solution
Saviynt checks the email as well as the data column ( user_attributes table ) before generating email address, so user_attributes can be used as a lookup table to store the email address so that it is captured during email address creation.
As there is no direct way to feed the data in user_attributes table we have exposed this table in inline processing as well as direct mapping in user import.
lets take AD as the target system, proxy address is the attribute which is being stored multiple emails. In the user import mapping you would need to provide the below json as example
[CUSTOMPROPERTY30::employeeID#String,
LOCATIONDESC::ssoId#String,
CUSTOMPROPERTY42::sAMAccountName#String,
USERATTRIBUTE_EMAIL:proxyAddresses#String,
USERATTRIBUTE_CHECK1:customproperty23#String]
Userattribute Table is directly exposed and you will be able to see this attribute in user update history table.
You can map multiple columns to USERATTRIBUTE_EMAIL OR USERATTRIBUTE_CHECK1 OR any naming convention, in the user attribute table it will be stored in attributename as Email or check1.
For all entries in userattribute table, while generating email the data column value will be checked.
Sample modify user data json
Sample Json:
{ "ADDITIONALTABLES":
{ "USERS": "SELECT USERKEY,firstname,lastname FROM USERS", "USER_ATTRIBUTES": "SELECT USERKEY, DATA, ATTRIBUTENAME FROM USER_ATTRIBUTES" },
"COMPUTEDCOLUMNS": [ "customproperty2", "customproperty3" ],
"PREPROCESSQUERIES": [ "UPDATE NEWUSERDATA, CURRENTUSERS cu SET CUSTOMPROPERTY2 = (select CONCAT(lastname, ', ', firstname) from CURRENTUSERS where userkey=1)", "UPDATE NEWUSERDATA SET CUSTOMPROPERTY3 = (select count(USERKEY) from currentusers)", "UPDATE NEWUSERDATA SET USERATTRIBUTE_EMAIL='email1,email2,email3' where USERATTRIBUTE_EMAIL like 'validation%'" ] }
You can set the userattribute_email accordingly and the data is split these into comma and entered these value in user_attribute table.
Ex:
Userattribute_email = "d1@gmail.com,d2@gmail.com,d3@gmail.com"
In the user attribute table, the data is entered as in each row split by comma so that all emails will checked in email generation rule.
References
