Bug 167112 - Objectclass inheritance mechanism in queries doesn't seem to work
Summary: Objectclass inheritance mechanism in queries doesn't seem to work
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: openldap
Version: 3.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jan Safranek
QA Contact: Jay Turner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-08-30 14:56 UTC by Chris Picton
Modified: 2015-01-08 00:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 18:55:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Chris Picton 2005-08-30 14:56:23 UTC
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):
openldap-2.0.27-17

How reproducible:
Always

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:

http://www.openldap.org/its/index.cgi/Software%20Bugs?id=2053;selectid=2053

Comment 1 RHEL Program Management 2007-10-19 18:55:05 UTC
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:
http://www.redhat.com/security/updates/errata/
 
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.