6.0.0-git
2018-12-16

[#7321] Turba LDAP driver causing empty binds
Summary Turba LDAP driver causing empty binds
Queue Turba
Queue Version 2.2.1
Type Bug
State Assigned
Priority 2. Medium
Owners Horde Developers (at)
Requester webadmin (at) ualberta (dot) ca
Created 2008-09-11 (3748 days ago)
Due
Updated 2008-09-12 (3747 days ago)
Assigned 2008-09-12 (3747 days ago)
Resolved
Milestone
Patch No

History
2008-09-12 01:45:03 Chuck Hagenbuch Assigned to Horde DevelopersHorde Developers
State ⇒ Assigned
 
2008-09-11 16:30:45 webadmin (at) ualberta (dot) ca Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ Turba LDAP driver causing empty binds
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
Reply to this comment
During the listing of address books in the horde sidebar, each address 
book source is instantiated with a Turba_Driver object. Basically to 
do some permission checks on the driver.



But, when we call the driver factory, some initialization method is 
called in the driver, and in the case of an LDAP driver, this method 
is connecting to the server.  The connections to the server are in the 
form of empty bind requests:



Sep  7 18:27:48 ldapcluster4 slapd[30038]: conn=11033182 fd=42 ACCEPT 
from IP=xxx.xxx.xxx.xxx:42243 (IP=0.0.0.0:389)

Sep  7 18:27:48 ldapcluster4 slapd[30038]: conn=11033182 op=0 BIND 
dn="" method=128

Sep  7 18:27:48 ldapcluster4 slapd[30038]: conn=11033182 op=0 RESULT 
tag=97 err=0 text=

Sep  7 18:27:49 ldapcluster4 slapd[30038]: conn=11033182 op=1 UNBIND

Sep  7 18:27:49 ldapcluster4 slapd[30038]: conn=11033182 fd=42 closed



These empty binds happen all over the place, causing large numbers of 
requests per session.  On a large installation it can result in half a 
million LDAP binds per day.



A temporary fix for this problem is to comment out the turba_menu 
section in /horde/config/registry.php.

Saved Queries