How to populate a user defined group?


Domino/Notes Version: 12 FP7
Add-on Product (if appropriate, e.g. Verse / Traveler / Nomad / Domino REST API):
Its Version:
Operating System:
Client (Notes, Nomad Web, Nomad Mobile, Android/iOS, browser version):


Problem/Query:

I wish to create a user defined group in the NAB which contains all users with the OU = ABC. In the selection criteria what syntax do I need to add to achieve this? I have tried using the LDAP Query syntax

(&(objectClass=dominoPerson)(distinguishedName=,ou=ABC,))

Is there any other type of selection criteria I can use or can anyone tell me why this LDAP Query does not work?

Hello Andrew,

Looks like there is no option available right now to create an auto-populated group based on the user’s OU in the hierarchical name. Found this enhancement request → custom criteria to populate groups based in | HCL Domino Ideas Portal

But you may try a workaround. Take any field(or a new one) in the person document and update the user’s OU there. Then create an LDAP filter for the auto-populated group.

For ex : Use the field “Department“ and set the same value in the OU, say “Sales“[User1/Sales/Acme]. Now use the filter like “(&(ObjectClass=person)(department=Sales))“

I hope this helps.

Thanks!

AutoPopulated groups work with LDAP filters. Domino LDAP filters are sometimes a little different from “normal” LDAP filters. I always use the included “ldapsearch.exe” to test LDAP filters.

Just open a command prompt and navigate to your HCL Notes program directory. There you can usually type:

ldapsearch.exe -h “YourFullyQualifiedServerName” “YourQuery”

If your server does not allow anonymous queries, then you need to add -D “YourUserName” -w “YourInternetPassword”

This filter works perfectly with ldapsearch.exe:

(&(objectClass=dominoPerson)(OU=ABC))

I didn’t see why this should not also work with an autopopulated group (as suggested in the other answer).

So I just tested this on my testserver and it worked perfectly

Did you test?`For me it seams that the idea is simply wrong…

You can test it !

Sorry, you misunderstood as I was not clear: Did you test the claim from the ideas site, as this one is wrong. Your solution works but is not necessary as OU can be queried directly…

Kindly check this documentation for your reference:

Yes, the syntax (&(objectClass=dominoPerson)(OU=ABC)) works correctly. Thanks a lot. The syntax I was using was not correct.

The syntax (&(objectClass=dominoPerson)(InternetAddress=abc)) also works but I managed to get the OU syntax working. See my other reply. Thanks for your help.