powered by Jive Software

Wildfire 3.2.3 Potential LDAP bug

I’'ve been struggling to get 3.2.3 to authenticate my users correctly.

I’'ve narrowed down the cause of this to a domain controller which is not contactable by the Wildfire server.

Network traces show that the Wildfire server repeatedly attempts to contact that server when authenticating users despite a completely different server being specified in the config file.

I’‘m unsure whether this is an issue with Windows picking domain controllers out of it’'s site, or Wildfire itself. However, only Wildfire user logon is affected.

Could anyone shed any light on why it’'s behaving this way, or any method of restricted the domain controllers it will attempt to use?