Turba LDAP Search and Object Classes

Hi,

It's a bit counter-intuitive that Turba comes with example object class 
definitions like

  'objectclass' => array('top',
      'person',
      'organizationalPerson',
      'inetOrgPerson'),

in its backends.php file, while those objectclasses are combined using "or" 
when constructing the LDAP query. (In ./lib/Driver/Ldap.php)

For one, this behaviour is different from the documented behaviour of the 
objectclass lists in the general Horde config and second, it probably returns 
much more results than expected on many LDAP servers, especially with a 
"scope" "sub" LDAP search instead of a "scope" "one" LDAP list on a single 
LDAP level.


Regards,

  Gunter




-- 
Horde mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]