[Date Prev][Date Next] [Chronological] [Thread] [Top]

(ITS#4688) Missing objectClass attribute in an ldapsearch

Full_Name: Ashish Gawarikar
Version: 2.3.27
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (

The messageStoreRecipient class is a subclass of messageRecipient and hence the
search succeeds. But, as per RFC 4512.

 When creating an entry or adding an 'objectClass' value to an entry,
   all superclasses of the named classes SHALL be implicitly added as
   well if not already present.
   Servers SHALL restrict modifications of this attribute to prevent
   superclasses of remaining 'objectClass' values from being deleted.

("SHALL" in those sentences denotes an absolute requirement; see
RFC 2119 for details.)

# bin/ldapsearch -x "(&(objectClass=messageRecipient)(mailRoutingAddress=admin@mc3.com))"
# extended LDIF
# LDAPv3
# base <> with scope subtree
# filter:
# requesting: ALL

# admin@mc3.com, SysAccounts, mc3.com
dn: mailRoutingAddress=admin@mc3.com,ou=SysAccounts,dc=mc3,dc=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
objectClass: extensibleObject
objectClass: messageStoreRecipient
mail: admin@mc3.com
mailRoutingAddress: admin@mc3.com
mailLocalAddress: admin@mc3.com
cn: admin
sn: admin
description: Admin account
mailHost: abcd
userPassword:: e1NTSEF9S2xMMlhvRjVibHBxVlZDYnQrbS9OTEgyME5qckpBZkw=

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1

# strings slapd | grep OpenLDAP | grep slapd
@(#) $OpenLDAP: slapd 2.3.27 (Sep 13 2006 07:47:17) $