Been searching the forums for a good hour of so looking at other peoples examples and what not trying to find a solution that fits my needs. Unfortunately I only got half of the setup working, I’'ll explain what I am after.
I have created a group called “Company Chat Users” Which is located in Active Directory:
Unless you want to break your users up into Jabber groups, there’'s no need to mess with LDAP groups in Wildfire. I need more details on what you are trying to do with the group filtering to help any further.
Well I resolved my problem today when I decided to install the new Wildfire version.
I had created a user called “Jabber” for authentication in AD and it was only a member of “Denied Users” which was denied access to all our corporate data and was removed from the “Domain Users” group, I thought it was working because it was authenticating and also returning my username. However it was only returning my username it was weird.
I found when entering the domain administrator details it worked 100% I delegated read access over our OU to the user and left them out of the “Domain Users” group and changed the search filters and now it’'s working 100%.
Authentication and search results return users only in the group.
I have created a group called “Company Chat Users” Which is located in Active Directory:
sAMAccountType is an index attribute in AD. It should return things which represent a Person object extended with Principal attributes (password, etc). You can optionallly exclude inetOrgPerson classes. This would leave you with Users in a default AD installation.