directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-936) Using unknown OIDs or OIDs of wrong schema elements as a returning attribute causes search operations to fail
Date Fri, 18 May 2007 21:55:16 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497052
] 

Emmanuel Lecharny commented on DIRSERVER-936:
---------------------------------------------

Hmmm... There are three different cases :
- usage of unknown Attributes. This has been fixed (forget about the previous coment, it was
totally wrong)
- usage of known attributes which are not part of the entry : for instance, an attribute not
belonging to any of the entry Objectclass MAY or MUST
- usage of known attributes which are in the MAY list, but not stored in the entry

The first bug has been fix. The second one generates an exception, it still has to be fixed.
The third one must be tested

> Using unknown OIDs or OIDs of wrong schema elements as a returning attribute causes search
operations to fail 
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-936
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-936
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.5.1
>         Environment: * ApacheDS 1.5.1 (SNAPSHOT)
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> * Windows XP Professional SP2
>            Reporter: Stefan Zoerner
>         Assigned To: Emmanuel Lecharny
>            Priority: Critical
>
> If I perform a search operation, and use wrong OIDs as returning attributes, this causes
an error:
> $ ldapsearch -h localhost -p 10389 -D "uid=admin,ou=system" -w secret -b "dc=example,dc=com"
-s sub "(objectClass=*)" 9.9.9
> ldap_search: Unknown error
> ldap_search: additional info: failed on search operation: attributeType w/ OID 9.9.9
not registered!
> $
> The expected result is that the 9.9.9 (as a unknown attribute type in text format) is
ignored.
> The problem does also occur with known OIDs of from schema elements (object classes,
for instance), like
> $ ldapsearch -h localhost -p 10389 -D "uid=admin,ou=system" -w secret -b "dc=example,dc=com"
-s sub "(objectClass=*)" 2.5.6.6
> ldap_search: Unknown error
> ldap_search: additional info: failed on search operation: attributeType w/ OID 2.5.6.6
not registered!
> $
> 2.5.6.6 is the OID of object class person -- it is also possible to use the object class
name instead, like
> $ ldapsearch -h localhost -p 10389 -D "uid=admin,ou=system" -w secret -b "dc=example,dc=com"
-s sub "(objectClass=*)" person
> ldap_search: Unknown error
> ldap_search: additional info: failed on search operation: attributeType w/ OID 2.5.6.6
not registered!
> $
> I assume, it is an error in the schema registries, or how they are used in searches.
> Fixing this error will likely resolve  DIRSERVER-927 as well.

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


Mime
View raw message