This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2219000 - subsuffix are not returned in one level scoped search
Summary: subsuffix are not returned in one level scoped search
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: 389-ds-base
Version: 11.8
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: DS12.5
: dirsrv-12.5
Assignee: Pierre Rogier
QA Contact: LDAP QA Team
Evgenia Martynyuk
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks: 2292903
TreeView+ depends on / blocked
 
Reported: 2023-06-30 21:31 UTC by mreynolds
Modified: 2024-06-26 13:53 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2292903 (view as bug list)
Environment:
Last Closed: 2024-06-26 13:53:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Case 03838109 (55 bytes, text/plain)
2024-06-06 16:26 UTC, eperuch 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 5772 0 None open subsuffix are not returned in one level scoped search 2024-06-18 07:48:03 UTC
Red Hat Issue Tracker   DIRSRV-56 0 None None Red Hat Issue Tracker 2024-06-26 13:53:27 UTC
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
Comment 1 eperuch 2024-06-06 16:26:25 UTC 
Created attachment 2036610 [details]
Case 03838109

This bug is critical for the customer, blocking them to upgrade from an unsupported version for which they are paying, RHDS 10.0.0 to 12.5
Comment 4 Lorenzo Fanni 2024-06-26 09:33:55 UTC 
Hi all,
today I just did a fresh install of RHEL 9.4 and installed RHDS 12.4.
I created a suffix (dc=fanni,dc=test) and a sub-suffix (ou=prova,dc=fanni,dc=test) but the behavior seems the same.
I attach a text file with the result of the query with scope "one": I still can't see the sub-suffix.
Comment 5 Lorenzo Fanni 2024-06-26 09:45:34 UTC 
(In reply to Lorenzo Fanni from comment #4)
> Hi all,
> today I just did a fresh install of RHEL 9.4 and installed RHDS 12.4.
> I created a suffix (dc=fanni,dc=test) and a sub-suffix
> (ou=prova,dc=fanni,dc=test) but the behavior seems the same.
> I attach a text file with the result of the query with scope "one": I still
> can't see the sub-suffix.

We need the product will work with the previous query option "-s one" like in the 10 RHDS version
Comment 7 Viktor Ashirov 2024-06-26 13:53:29 UTC 
This BZ has been automatically migrated to Red Hat Issue Tracker https://issues.redhat.com/browse/DIRSRV-56. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.