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 th…

Its odd. So I went back to your default example
I have a domain Local Security group called = Openfire Access Group
I have 2 global security groups Group1_im and Group2_im which are members of Openfire Access Group
My account is a member of Group1

Base DN is DC=ad,DC=domain,DC=edu

group search filter is (&(objectClass=group)(cn=*_im))

I set this. Restart the service. I look into groups and see Group1_im and Group2_im

I set the user search filter to (&(objectclass=organizationalPerson)(|(memberOf:1.2.840.113556. 1.4.1941:=CN=Openfire Access Group,CN=Users,DC=ad,DC=domain,DC=edu))((userAccountControl:1.2.840.113556.1.4. 803:=2)))

Basically, the issue is you have a space hidden somewhere in the user search statement. This causes it to become an invalid statement so Openfire will not pick up users.

I would recommend copying the statement into notepad and doing a search and replace for any spaces or just manually search it.

The search and replace should work. I was annoyed and stupid at the time of fixing my issue and never thought of doing a search and replace and just did it manually.

Once you remove all the spaces and confirm it works, I would recommend saving the statement to a file (so you don’t have to deal with this again).

When I put the statement in Openfire I noticed a red squiggly below the statement (the same one you get when you spell something wrong in Word). If you see this and it is broken up, you probably have a space somewhere.