https://bugs.openldap.org/show_bug.cgi?id=10432
Ondřej Kuzník <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Ondřej Kuzník <[email protected]> --- Unfortunately yes, if you review RFC 4511, section 4.5.1.7, when using an invalid attribute description: A filter item evaluates to Undefined when the server would not be able to determine whether the assertion value matches an entry. ... For example, if a server did not recognize the attribute type shoeSize, the filters (shoeSize=*), (shoeSize=12), (shoeSize>=12), and (shoeSize<=12) would each evaluate to Undefined. >From that, an Undefined value will negate to Undefined, then through an AND can only evaluate to FALSE or Undefined, neither matching any entry. -- You are receiving this mail because: You are on the CC list for the issue.
