I am confused about how this works. I’‘d like to be able to provide a basedn to the ldap auth process in wildfire. I then would like wildfire to use that basedn with a user’‘s provided uid and try an authenticated bind using that user’‘s dn. This log below seems to indicate that wildfire is doing way more work than it needs to: searching and i don’'t know what else. During times of heavy load, the wildfire server gets really bogged down.
What all is it trying to do? I am concerned about all this extra churn. I don’‘t use groups from ldap, I am not populating vcards with ldap data. Here is my ldap config section. We’'re using 3.1.1:
<!636>
<!true>
2006.12.15 16:29:22 Trying to find a user’'s DN based on their username. uid: ffarooq1, Base DN: ou=People,ou=Intranet,dc=yy,dc=com…
2006.12.15 16:29:22 Creating a DirContext in LdapManager.getContext()…
2006.12.15 16:29:22 Created hashtable with context values, attempting to create context…
2006.12.15 16:29:22 … context created successfully, returning.
2006.12.15 16:29:22 Starting LDAP search…
2006.12.15 16:29:22 … search finished
2006.12.15 16:29:22 In LdapManager.checkAuthentication(userDN, password), userDN is: motguid=“FFAROOQ1”…
2006.12.15 16:29:22 Created context values, attempting to create context…
2006.12.15 16:29:22 … context created successfully, returning.
2006.12.15 16:29:24 … context created successfully, returning.
2006.12.15 16:29:24 Starting LDAP search…
2006.12.15 16:29:24 … search finished
2006.12.15 16:29:24 Creating a DirContext in LdapManager.getContext()…
2006.12.15 16:29:24 Created hashtable with context values, attempting to create context…
2006.12.15 16:29:24 … context created successfully, returning.