Active Directory Search Field Length

[Jason_L]

I am working to migrate from our old 3.5.1 install to a new 4.1 install. Everything got setup just fine on the new server and I am able to connect to my active directory server. The problem is the user search field is not long enough for my search filter and I can’t seem to use a wild card. Below is an example search:
(objectClass=organizationalPerson)(|(memberOf=cn=chat_it,ou=security groups, dc=our, dc=company, dc=com))

That works just fine. But I have lots of groups that start with chat_… and want to filter to all of those people just in those groups. I tried changing the cn to
memberOf=cn=chat_*
Also tried using a % and neither worked at all. The other issue is we have more users then the paging limit in AD so I need to narrow the list of users. I also only want to let certain users login. I am doing a group filter to just these groups and have no issues there. Help is appreciated.

[speedy]

this is how I do it. perhaps this will help you out.

How to Setup Authentication Groups with LDAP/AD

In this example I’ll be using the following: AD domain = AD-DOMAIN.local access group = Openfire Access Group roster groups = _IM Group1, _IM Group2 (*note - I’ll be using _IM as part of a wildcard search, so all my groups start with _IM for that reason) First create your security groups: Create a Domain Local Security Group. In our example call it Openfire Access Group. In this example, I’ve placed the group in the user container. Create regular security groups (usually Global). In t…

you can edit the field directly in the DB or from within the system properties page.

also, to get around the AD paging limit, add this to your system properties
ldap.pagedResultsSize with a value of 1000