directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Karasulu <aok...@bellsouth.net>
Subject Re: Complex filter not recognized properly
Date Sat, 17 Jun 2006 05:22:15 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vladimir Gjokevski wrote:
> Hi,
> I have created a custom partition that is responsible for serving PGP
> keys, and i have the following
> problem:
> 
> when issuing with ldapsearch the following command:
> 
> ldapsearch -x -H ldap://localhost:11500 -D "dn=bugs" -w bunny -b
> "dc=pgpkeys" "(&(pgpuserid=test*)(pgpdisabled=0))"
> 
> in the search() method of my custom partition class I get a SimpleNode
> filter with just (pgpdisabled=0) instead
> of more complex filter i guess it should be a BranchNode object that
> will represent the filter "(&(pgpuserid=test*)(pgpdisabled=0))"
> sent by the client.

Hi Vladimir,

Yes this is the expected result if you have not defined pgpuserid as a
valid schema attribute.  Basically the server ignores terms (actively
trimming them from the filter's AST) if they are not defined attributes.

LDAP specifies that undefined attribute value assertions in filters are
to be ignored hence the pruning.

To work around this make sure you add pgpuserid in a custom schema to
apacheds.  If you've already done this, make sure you have spelled the
attribute identifier correctly.

HTH,
Alex
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEk5GHPVto+tI7JJARAnM6AKD7Yjffr5CKlRgLy+iA4rlDPwT/nQCfRty2
+vSXSnFwOriuA/mAAqyl6QU=
=ld9Q
-----END PGP SIGNATURE-----

Mime
View raw message