Christian Kratzer wrote:
very interesting point.
I have a customer with an enterprise application that insists on having an explicit objectClass: top on all entries.
Their developers argue that the rfcs mandate an explicit objectClass: top on all entries. I argue that the wording in the respective rfcs is not exact enough. Having an objectClass that inherits from top should be enough from my point of view.
I am currently travelling and cannot lookup the rfc.
I vaguely remember having researched this as well many years ago. Don't remember the details but I came up with the following recommendations:
For client developers: Don't require object class 'top'.
For LDAP admins: Add object class 'top' to all entries.
Ciao, Michael.