You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Zoerner (JIRA)" <ji...@apache.org> on 2007/05/18 11:03:16 UTC
[jira] Created: (DIRSERVER-936) Using unknown OIDs or OIDs of wrong
schema elements as a returning attribute causes search operations to fail
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
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.
[jira] Commented: (DIRSERVER-936) Using unknown OIDs or OIDs of
wrong schema elements as a returning attribute causes search operations to
fail
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497771 ]
Stefan Zoerner commented on DIRSERVER-936:
------------------------------------------
The issue has never been in 1.0. I have just retested the 1.0.2-SNAPSHOT just to be sure.
And I have rebuild the current ApacheDS trunk in order to check the 1.5. Everything works fine for me. All problematic cases I know perfectly work. Well done, Emmanuel!
> 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.
[jira] Resolved: (DIRSERVER-936) Using unknown OIDs or OIDs of
wrong schema elements as a returning attribute causes search operations to
fail
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-936.
-----------------------------------------
Resolution: Fixed
Ok, as Stefan has double checked the fix, I mark it as resolved.
Thanks Stefan, you did a perfect job testing it and double checking the fix !
> 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.
[jira] Commented: (DIRSERVER-936) Using unknown OIDs or OIDs of
wrong schema elements as a returning attribute causes search operations to
fail
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497020 ]
Emmanuel Lecharny commented on DIRSERVER-936:
---------------------------------------------
The SchemaService attributes filtering method was doing exactly the opposite thing that it was suposed to do :
- instead of removing the unkown attributes from the list of attributes to return, it removed the known attributes ...
So not only you have a problem in respect to the RFC (if the attribute is unkown, just ignore it), but you won't even see the requested attributes...
The fix was just a question fo inverting the test ( removing a !), plus dealing with a special case, when the list is empty after having removed all the attributes (NPE was generated in this case).
Tests are being added atm...
> 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.
[jira] Assigned: (DIRSERVER-936) Using unknown OIDs or OIDs of
wrong schema elements as a returning attribute causes search operations to
fail
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny reassigned DIRSERVER-936:
-------------------------------------------
Assignee: Emmanuel Lecharny
> 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.
[jira] Closed: (DIRSERVER-936) Using unknown OIDs or OIDs of wrong
schema elements as a returning attribute causes search operations to fail
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny closed DIRSERVER-936.
---------------------------------------
closed
> 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
> Assignee: 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.
[jira] Commented: (DIRSERVER-936) Using unknown OIDs or OIDs of
wrong schema elements as a returning attribute causes search operations to
fail
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497079 ]
Emmanuel Lecharny commented on DIRSERVER-936:
---------------------------------------------
Little modification in the previous comment. We have more cases :
1) Usage of unkown attributes (unkown means not declared in the schema) : fixed
2) Usage of known attributes, but not in MAY or MUST (there are some special cases fith operational attributes). To be tested
3) Usage of a known OID which is not an AttributeType : fixed
4) Usage of known attributes which are in the MAY list, but not stored in the entry. To be tested
5) Usage of a known attribute which has been disabled. To 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.
[jira] Commented: (DIRSERVER-936) Using unknown OIDs or OIDs of
wrong schema elements as a returning attribute causes search operations to
fail
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497647 ]
Emmanuel Lecharny commented on DIRSERVER-936:
---------------------------------------------
Ok, fixed in trunk :
http://svn.apache.org/viewvc?view=rev&rev=540369
tests added :
http://svn.apache.org/viewvc?view=rev&rev=540366
I'm not sure that the 1.0.1 server is impacted at all, I have run the same tests, and they are running ok.
Stefan, can you double check on 1.5 and 1.0 ?
Thanks !
> 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.
[jira] Commented: (DIRSERVER-936) Using unknown OIDs or OIDs of
wrong schema elements as a returning attribute causes search operations to
fail
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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.