Bug 167112 - Objectclass inheritance mechanism in queries doesn't seem to work
Objectclass inheritance mechanism in queries doesn't seem to work
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: openldap (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jan Safranek
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2005-08-30 10:56 EDT by Chris Picton
Modified: 2015-01-07 19:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 14:55:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Picton 2005-08-30 10:56:23 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050627 Firefox/1.0.4

Description of problem:
I have a ldap db which has objects which have the following objectclass:
objectClass: InetOrgPerson

When running queries which look for objectClass=person, the above objects are not returned as part of the search.

They should be, as objectClass InetOrgPerson inherits from objectClass person.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create an ldap entry which has objectClass=InetOrgPerson, and NOT objectClass=person
2. Search for (objectClass=person)

Actual Results:  The expected entry was not found

Expected Results:  The expected entry should have been found

Additional info:

This bug was fixed in openldap circa August 2002.  See here for details:

Comment 1 RHEL Product and Program Management 2007-10-19 14:55:05 EDT
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

Note You need to log in before you can comment on or make changes to this bug.