[Tickets #9197] Group Listing returns fatal error

bugs at horde.org bugs at horde.org
Tue Aug 24 17:08:57 UTC 2010


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

Ticket URL: http://bugs.horde.org/ticket/9197
------------------------------------------------------------------------------
  Ticket             | 9197
  Created By         | hutter at ihs.ac.at
  Summary            | Group Listing returns fatal error
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


hutter at ihs.ac.at (2010-08-24 13:08) wrote:

Setup: H4 latest git code and Active Directory on Windows 2000 Server

Clicking on Groups (logged in as administrator) returns the following
error:
A fatal error has occurred
Could not reach the LDAP server
[line 556 of .../horde/framework/Group/lib/Horde/Group/Ldap.php]

Looking at the code (horde/framework/Group/lib/Horde/Group/Ldap.php)
you find the folowing snippet:
        if (isset($this->_params['binddn'])) {
            $bind = @ldap_bind($this->_ds, $this->_params['binddn'],
                               $this->_params['password']);
        } else {
            $bind = @ldap_bind($this->_ds);
        }

        if (!$bind) {
            throw new Horde_Group_Exception('Could not bind to LDAP server');
        }

Well I don't know why one don't see the error "Could not bind to LDAP Server",
maybe it's overwritten by the following Horde_Group_Exeption from the
ldap_search call. Nevertheless, binddn is empty, so an anonymous bind is
tried. Windows 2008 AD Server prevents anonymous binds by default. I couldn't
find any setting in the conf.php named "binddn" nor any in conf.php.dist.
So I replaced those with searchdn (password with searchpw) and it works.

Note: The Group Listing is still empty (as in H3) but this seems to be  
another problem I'm trying to track down in the code.







More information about the bugs mailing list