Click HERE to see how Saviynt Intelligence is transforming the industry. |
09/07/2023 02:38 AM
Hi all,
We have configured the checkforunique parameter to check for CN uniqueness for AD connection. However, we're getting an error when provisioning the account. In the logs, we can see that the CN is not appended. There is an existing account with the same firstname lastname so we are expecting the checkforunique json to set the cn value as ${user.firstname} ${user.lastname}1. The cn value in the logs shows ${user.firstname} ${user.lastname}
Appreciate any help on this
CHECKFORUNIQUE json:
{"cn":"${user.firstname} ${user.lastname}###${user.firstname} ${user.lastname}1###${user.firstname} ${user.lastname}2###${user.firstname} ${user.lastname}3"}
Solved! Go to Solution.
09/11/2023 01:41 AM
Hi @println-titan,
Thanks for reaching saviynt forum,you can find more details on this in the forum post below:-
https://forums.saviynt.com/t5/identity-governance/checkforunique-is-not-triggered/m-p/27505
Please valiadte and let us know if further assistance is needed on this.