Click HERE to see how Saviynt Intelligence is transforming the industry. |
03/14/2023 01:55 AM
Hello, i am tryng to use CHECKFORUNIQUE json in AD connection but is not getting triggered. In task I saw an error that account with same accountName is existing in AD (I created few user object in AD with the same account name and UPN as testing users).
In CREATEACCOUNTJOSN i have defined mapping for sAMAccountName and UPN:
"sAMAccountName":"${user.systemUserName}",
"userPrincipalName": "${user.systemUserName+'@domain.net'}",
And this is defined in CHECKFORUNIQUE
{
"sAMAccountName":"${user.systemUserName}###${user.systemUserName}1###${user.systemUserName}2",
"userPrincipalName":${user.systemUserName}@domain.net###${user.systemUserName}1@domain.net###${user.systemUserName}2@dom...
}
Can somebody explain how this work? When does it fallback to CHECKFORUNIQUE rules?
Thank you!
03/14/2023 02:09 AM
CHECKFORUNIQUE feature will be evaluated while doing provisioning.
As per the above json , its looks valid, As per the logs is it evaluating all the 3 conditions or its not evaluating at all, can you attach the snippet of logs.
Thanks
Darshan
05/11/2023 12:02 PM
this worked?not working for me
06/08/2023 09:23 AM