Bug 2219000 - subsuffix are not returned in one level scoped search
Summary: subsuffix are not returned in one level scoped search
Keywords:
Status: NEW
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: 389-ds-base
Version: 11.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: LDAP Maintainers
QA Contact: LDAP QA Team
Evgenia Martynyuk
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-30 21:31 UTC by mreynolds
Modified: 2023-07-03 13:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker IDMDS-3293 0 None None None 2023-06-30 21:34:10 UTC

Description mreynolds 2023-06-30 21:31:06 UTC
Description of problem:

subsuffix are not returned in one level scoped search

Steps to reproduce the behavior:

- Create an instance with dc=example,dc=com suffix (with entries in the backends)
- Create a subsuffix just below the suffix with entries:
- dsconf instance backend create --suffix ou=foo,dc=example,dc=com --create-entries --be-name foo
- Run ldapsearch ldapsearch with sub scope:

    ldapsearch -Q -LLL -Y EXTERNAL -H ldapi://%2fvar%2frun%2fslapd-i1.socket -s sub -b dc=example,dc=com '(ou=*)' dn
    (No errors: ou=foo,dc=example,dc=com is listed)

- Run ldapsearch with one scope:

    ldapsearch -Q -LLL -Y EXTERNAL -H ldapi://%2fvar%2frun%2fslapd-i1.socket -s one -b dc=example,dc=com '(ou=*)' dn
    (Error: ou=foo,dc=example,dc=com is not listed)

Expected results

    ou=foo,dc=example,dc=com should be listed in both cases

Additional context

    This behavior confuses some ldap browsers that cannot show any more the entries below sub suffix.

Upstream ticket:

    https://github.com/389ds/389-ds-base/issues/5772


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