Fix a bug in filterLDAP::get_list which gets triggered, if the class is used with multiple storage points and the search shall return objects in the search base.
Bugfix for trac #8028
Fix a bug in filterLDAP::get_list which gets triggered, if the class is
used with multiple storage points and the search shall return objects in
the search base.
In this case the function would return much to many objects,
since multiple queries with scope LDAP_SCOPE_SUBTREE are issued, while
the query on the initial base should use LDAP_SCOPE_ONE instead.
This commit fixes this bug, by checking the base of the query against
the initial base and using a LDAP_SCOPE_ONE search, if initial base and
currently processed base are equal.
taken from limux-gosa git commit ece6a3bcf79c771ddab7404529937575b74277b8
Cheers
(from redmine: issue id 1065, created on 2012-06-13, closed on 2012-11-30)
- Changesets:
- Revision 4b77926a by Benoit MORTIER on 2012-06-13T08:04:48.000Z:
Fixes: #1065 Fix a bug in filterLDAP::get_list which gets triggered, if the class is used with multiple storage points and the search shall return objects in the search base.
- Revision fded835f by Benoit MORTIER on 2012-06-25T15:27:04.000Z:
Fixes: #1065 Fix a bug in filterLDAP::get_list which gets triggered, if the class is used with multiple storage points and the search shall return objects in the search base.
- Custom Fields:
- Bug in version: 1.0.4