Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Descriptionrick.beldin@hpe.com
2016-09-21 17:34:35 UTC
Document URL:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/System-Level_Authentication_Guide/index.html
Same issue on RHEL 7.3 beta document
Section Number and Name:
9.3.2 Changing the Database-Specific Configuration
By default, the OpenLDAP server uses Berkeley DB (BDB) as a database back end.
The configuration for this database is stored in the
/etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif file.
Describe the issue:
The file does not exist.
# pwd
/etc/openldap/slapd.d/cn=config
[root@rhel72-ldap cn=config]# ls -1
cn=schema
cn=schema.ldif
olcDatabase={0}config.ldif
olcDatabase={-1}frontend.ldif
olcDatabase={1}monitor.ldif
olcDatabase={2}hdb.ldif
Suggestions for improvement:
Document the files delivered and the defaults. The man page for SLAPD-BDB says:
The bdb backend to slapd(8) uses the Oracle Berkeley DB (BDB) package to
store data. It makes extensive use of indexing and caching to speed data
access.
Note that BDB is deprecated and support will be dropped in future OpenL‐
DAP releases. Installations should use the mdb backend instead.
This is not reflected in the documentation.
Additional information:
Comment 1rick.beldin@hpe.com
2016-09-21 17:45:32 UTC
Doc issue only in RHEL 7.3 beta documentation.
7.2 doesn't have the chapter.
Comment 3Aneta Šteflová Petrová
2016-09-22 09:35:03 UTC
Thank you for the report. Marc, can you please look into this?
I updated the "Database-Specific Configuration" section. It shows now the correct file name, describes the correct default database back end (hdb), and notes that BDB is deprecated.
Additionally I added short sections to describe the other two files in /etc/openldap/slapd.d/cn=config/: olcDatabase={-1}frontend.ldif and olcDatabase={1}monitor.ldif
We will republish the updated guide after RHEL 7.3 GA (2016-10-25).
Please note that we are currently thinking about moving the OpenLDAP chapter back to the System Administrator's Guide. In this case look for the updated section in the System Administrator's Guide after GA.
Comment 7rick.beldin@hpe.com
2016-09-29 14:57:04 UTC
I think moving this back to the Sys Admin Guide might not be a bad idea.
If you do, I think you need to beef up the section on setting this up. The OpenLdap 2.4 configuration files are considerably different than before and the information is insufficient for someone to follow and have a minimal functioning LDAP server. Most of the existing documentation consists of making edits to /etc/openldap/slapd.conf, which is now deprecated. The 'new' way of doing things is to use ldapmodify, but basic instructions on how to change the rootDN password and other other basic attributes are unclear.
Comment 8Aneta Šteflová Petrová
2016-11-04 08:39:14 UTC
The updated content is now available on the Customer Portal.