directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Zoerner (JIRA)" <>
Subject [jira] Created: (DIRSERVER-1330) Using a filter with present match with unknown attribute type causes error (error code 16)
Date Sun, 15 Mar 2009 20:34:50 GMT
Using a filter with present match with unknown attribute type causes error (error code 16)

                 Key: DIRSERVER-1330
             Project: Directory ApacheDS
          Issue Type: Bug
    Affects Versions: 1.5.5
         Environment: Windows XP
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
ApacheDS 1.5.5 SNAPSHOT
Apache Directory Studio 1.3.0, or any other LDAP client
            Reporter: Stefan Zoerner

If I use a search filter with unknown attribute type, like (blah=*), ApacheDS returns an error
code 16:

$ ldapsearch -h localhost -p 10389 -D "uid=admin,ou=system" -w secret -b "ou=system" -s one
"(blah=*)" dn

ldap_search: No such attribute
ldap_search: additional info: NO_SUCH_ATTRIBUTE: failed for     SearchRequest
        baseDn : ''
        filter : '(blah=*)'
        scope : single level
        typesOnly : false
        Size Limit : no limit
        Time Limit : no limit
        Deref Aliases : never Deref Aliases
        attributes : 'dn'
: OID for name 'blah' was not found within the OID registry

Expected behavior is an empty result set. I have checked this with other LDAP servers (OpenLDAP
2.3, Sun DS 5.2, Tivoli DS 6.0), which behave like that. 

RFC 2251 states "The present match evaluates to TRUE where there is an attribute or subtype
of the specified attribute description present in an entry, and FALSE otherwise (including
a presence test with an unrecognized attribute description.)" (section 4.5.1).

The more recent RFC 4511 states "Servers MUST NOT return errors if attribute descriptions
or matching rule ids are not recognized, assertion values are invalid, or the assertion syntax
is not supported." (section SearchRequest.filter)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message