Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-49458

subsuffix are not returned in one level scoped search

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • rhel-9.5
    • None
    • 389-ds-base
    • 389-ds-base-2.5.2-1.el9
    • None
    • None
    • ZStream
    • sst_idm_ds
    • 25
    • 0
    • QE ack, Dev ack
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Approved Blocker
    • Bug Fix
    • Hide
      .One-level scoped search no longer fails to return sub-suffixes

      Previously, when you ran the `ldapsearch` command with the `-s` option set to `one`, the search result did not contain sub-suffixes of the entry specified in the `-b` option. With this update, the one-level scoped search successfully returns immediate children of the entry.
      Show
      .One-level scoped search no longer fails to return sub-suffixes Previously, when you ran the `ldapsearch` command with the `-s` option set to `one`, the search result did not contain sub-suffixes of the entry specified in the `-b` option. With this update, the one-level scoped search successfully returns immediate children of the entry.
    • Done
    • None

      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

              progier Pierre Rogier
              rhn-engineering-mareynol Mark Reynolds
              IdM DS Dev IdM DS Dev
              IdM DS QE IdM DS QE
              Evgenia Martyniuk Evgenia Martyniuk
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: