[Date Prev][Date Next]
Pierangelo Masarati wrote:
I think I've spotted the problem. For some reason I can't remember
(nor explain at the moment) I removed that part of the condition for
ldap_entry_objclasses. I'm considering the opportunity to put it
back, since it largely reduces the amount of candidates selected when
filtering for an "auxiliary" objectClass and, at the moment, I don't
see any drawback.
I've found the reason: that part was removed because it would have
conflicted with composite filters; your problem should now be fixed in
HEAD (please confirm).
SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497