This content has been marked as final. Show 3 replies
Entries, attribute types, attribute values, and attribute options are never ordered, that is, the ordering is not repeatable. For more information, see http://www.ldapguru.info/ldap/ordering.html
Thank you for your information but this isn't about ordering.
It is about ldap appearing to ignore any objectclass that greater than 5 in a list of objectclasses.
I don't expect to see objectclass X as the first one returned I just expect it to be returned in any order when a search is performed for
As long as both objectclass X and attribute Y exist I should get a return regardless of order.
But when I dump a user to LDIF I find that objectclass X is the 6-x of all of the users objectclasses the search failes.
Can you reproduce this using ldapsearch? It would be useful to see the command line you use to produce this behavior along with access log snippets from the server that correspond with the failed search.