I hope that you did remove “<!” before and “>” after the LDAP section. If you change “ADserver” or “389” to something which is not an LDAP server then wildfire will complain in the logs during startup that it can not connect to LDAP.
@ 1. Wildfire searches in LDAP,
@ 2. so adding users to Wildfire makes no sense
@ 3. The xmpp.domain is the one of your jabber server and has nothing to do with LDAP.
However, if I did decide to rename the current OU “Active Accounts” to Active_accounts", would that break any of the other programs that rely on AD for authenication?
I dont want to have to change the whole infrastructure (eg. deployment etc…) to get WF to work.
Huh, interesting. Spaces in group names causing issues is not a known issue. Can anyone else confirm? If so, i’'ll file an issue and see if we can get a fix in place.
We identified this a while ago. somethign about the spaces and the %20% stuff. here’'s one example of spaces creating an issue, there are more from around the same time frame.
Don’'t rename the group, create a new one, and assign your users into it. Windows is supposed to be ‘‘dynamic’’ but just like windows firewall, anti-virus, and security you gotta take that with a grain of salt. Create a group named IM or something, add you and a couple of folks into it, then change your baseDN to look at that group. if you can log in, then you know it works.
one may track the progress of the issue here: JM-703
LG
PS @ Allxis: Don’'t spend your points here when you mark this question as answered, Jeff did help you much more to solve the problem than this issue does.