Univention Bugzilla – Bug 36343
mdb backend finds base object by ldapsearch -s one -b "$ldap_base" objectclass=domain
Last modified: 2016-05-10 12:30:25 CEST
I filed an upstream bug for this, see URL. Code using SCOPE_ONELEVEL searches may show a change of behaviour. From a quick grep I see these candidates: univention-licence/lib/license_ldap.c univention-python/uldap.py univention-python/modules/uldap.py univention-directory-listener/src/filter.c univention-directory-listener/tests/test__filter__cache_entry_ldap_filter_match.c univention-directory-manager-modules/scripts/proof_uniqueMembers E.g. I would expect "base+one" in univention.uldap to return the base object twice when searching e.g. for objectclass=domain. But the issue only occurs if a filter was specified for a scope "one" search which only matches the base of the search and none of the children. +++ This bug was initially created as a clone of Bug #36169 +++
Created attachment 6265 [details] fix_mdb_onelevel_search.patch Upstream patch.
cherry picked openldap from errata4.0-1 to errata4.0-3, added patch 97_bug36343.patch and built openldap in errata4.0-3. YAML: 2015-09-11-openldap.yaml
Ok, patch applied. ============== Applying patch 97_bug36343.patch using -p1 Output of the patch process: patching file servers/slapd/back-mdb/search.c OK ============== and "univention-ldapsearch -s one objectClass=univentionBase -LLL dn" works. Advisory is ok, I removed support for ucs4.0-2, which has has ended today.
<http://errata.software-univention.de/ucs/4.0/324.html>