[horde] Turba LDAP Search and Object Classes

[Jan Schneider]

Zitat von Ralf Lang <lang at b1-systems.de>:

> Am 12.09.2018 um 17:08 schrieb Jan Schneider:
>>
>> Zitat von Gunter Ohrner <mails.lists.horde.org at gunter.ohrner.net>:
>>
>>> 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
>>
>> What do you suggest? It's been this way since always, so just changing
>> it to "and" is not an option.
>>
> We cannot, at least for now, change how it's interpreted but we can
> change the example (remove the "top" class and document with a comment
> that it's OR)
> Maybe that reduces confusion.

+1

-- 
Jan Schneider
The Horde Project
https://www.horde.org/