RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2170494 - Obsolete nsslapd-ldapimaprootdn attribute
Summary: Obsolete nsslapd-ldapimaprootdn attribute
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: 389-ds-base
Version: 9.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 9.3
Assignee: Simon Pichugin
QA Contact: LDAP QA Team
Evgenia Martynyuk
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-16 14:22 UTC by Viktor Ashirov
Modified: 2023-11-07 09:10 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-2.3.4-1.el9
Doc Type: Deprecated Functionality
Doc Text:
.The `nsslapd-ldapimaprootdn` parameter is deprecated In Directory Server, the `nsslapd-ldapimaprootdn` configuration parameter is used to map a system root entry to a root DN entry. Usually, the `nsslapd-ldapimaprootdn` parameter has the same value as the `nsslapd-rootdn` parameter. In addition, changing one attribute but not changing the other leads to a non-functional autobind configuration that breaks `dsconf` utility and access to the web console. With this update, Directory Server uses only the `nsslapd-rootdn` parameter to map a system root entry to a root DN entry. As a result, the `nsslapd-ldapimaprootdn` parameter is deprecated and the root DN change does not break `dsconf` utility and access to the web console.
Clone Of:
Environment:
Last Closed: 2023-11-07 08:25:17 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 5697 0 None open Obsolete nsslapd-ldapimaprootdn attribute 2023-03-15 01:33:58 UTC
Red Hat Issue Tracker IDMDS-2825 0 None None None 2023-03-01 16:27:43 UTC
Red Hat Issue Tracker IDMDS-3431 0 None None None 2023-07-19 15:14:02 UTC
Red Hat Issue Tracker RHELPLAN-148914 0 None None None 2023-02-16 14:23:34 UTC
Red Hat Product Errata RHBA-2023:6350 0 None None None 2023-11-07 08:25:47 UTC

Description Viktor Ashirov 2023-02-16 14:22:14 UTC 
Description of problem:
LDAPI code uses nsslapd-ldapimaprootdn to map Unix root entry to a Root DN entry. It usually has the same value as nsslapd-rootdn. Changing one attribute but not changing the other leads to a non-functional autobind configuration that breaks dsconf and WebUI.

LDAPI code should use nsslapd-rootdn value instead of having two separate entries that should be kept in sync. This should make changing Root DN simpler and without fear that it will break dsconf or WebUI access.

See https://bugzilla.redhat.com/show_bug.cgi?id=2127795 for context.
Comment 1 Viktor Ashirov 2023-07-28 08:09:39 UTC 
Build tested: 389-ds-base-2.3.4-2.el9.x86_64

[1] dsconf changes only nsslapd-rootdn when RootDN is updated (previously both nsslapd-rootdn and nsslapd-ldapimaprootdn were changed): 

# dsconf -D cn=Directory\ Manager ldap://localhost config replace nsslapd-rootdn="cn=admin"
Enter password for cn=Directory Manager on ldap://localhost:
Successfully replaced "nsslapd-rootdn"


[2] When nsslapd-ldapimaprootdn is updated, dsconf logs a message:

# dsconf -D cn=Directory\ Manager ldap://localhost config replace nsslapd-ldapimaprootdn="cn=admin"
Enter password for cn=Directory Manager on ldap://localhost:
Successfully replaced "nsslapd-ldapimaprootdn"
The "nsslapd-ldapimaprootdn" setting is obsolete and kept for compatibility reasons. For LDAPI configuration, "nsslapd-rootdn" is used instead

And in the errors log:
[28/Jul/2023:03:54:30.718130078 -0400] - WARN - config_set_ldapi_root_dn - The "nsslapd-ldapimaprootdn" setting is obsolete and kept for compatibility reasons. For LDAPI configuration, "nsslapd-rootdn" is used instead.

In cn=config new value is also present: 
# ldapsearch -LLL -D cn=Directory\ Manager -w password -H ldap://localhost -s base -b cn=config nsslapd-rootdn nsslapd-ldapimaprootdn
dn: cn=config
nsslapd-rootdn: cn=Directory Manager
nsslapd-ldapimaprootdn: cn=admin

And autobind continues to work, since nsslapd-rootdn is now used, instead of nsslapd-ldapimaprootdn

# dsconf localhost backend suffix list
dc=example,dc=com (userroot)
# echo $?
0

[28/Jul/2023:04:08:03.981381558 -0400] conn=14 fd=64 slot=64 connection from local to /run/slapd-localhost.socket
[28/Jul/2023:04:08:03.985945222 -0400] conn=14 AUTOBIND dn="cn=Directory Manager"
[28/Jul/2023:04:08:03.987695893 -0400] conn=14 op=0 BIND dn="cn=Directory Manager" method=sasl version=3 mech=EXTERNAL

Marking as Verified:Tested
Comment 6 errata-xmlrpc 2023-11-07 08:25:17 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (389-ds-base bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6350
Note You need to log in before you can comment on or make changes to this bug.