[Tickets #7321] Turba LDAP driver causing empty binds

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7321
------------------------------------------------------------------------------
  Ticket             | 7321
  Created By         | webadmin at ualberta.ca
  Summary            | Turba LDAP driver causing empty binds
  Queue              | Turba
  Version            | 2.2.1
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


webadmin at ualberta.ca (2008-09-11 12:30) wrote:

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.