Hi everyone
We have been trying to use isUniqueLDAPValue in a before provisioning rule for our LDAP source to check uniqueness of some email attributes and it seems to be returning false when we expect the result to be true. Using the same method on our AD source however, does return true when we expect it. Does anyone have any experience using this method with sources using the LDAP connector and encountered a similar issue?
For further clarification, we are using this method because it does a search on the source and not just the existing accounts in IDN. We have filters in IDN so we cannot just search IDN. The method is not throwing an error, and we are using the identity and app IDs as the first 2 parameters in the method - it says in the docs that an error will be thrown if the identity or app cannot be found, so this is not the issue. We have tried doing an LDAP search ourselves with the attributeName and attributeValue parameters that we put in the rule, and this has returned no results (so this means the value is unique). We have put “mail” and “mailAlternateAddress” as the attributeValue in 2 separate isUniqueLDAPValue operations, and put the test mail (e.g. [email protected]) in the attributeName parameter. We have not made these attributes searchable as I believe that is to make them searchable in IDN and this method should search the source directly.