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.

Created attachment 484213 [details]
Test case

Description of problem:

When setting TLSCACertificatePath to NSS DB, SSL/TLS does not work.

Version-Release number of selected component (if applicable):

openldap-2.4.23-12.el6

How reproducible:

Always.

Steps to Reproduce:

1. install beakerlib
2. download attached test
2. bash runtest.sh
  
Actual results:

:: [   PASS   ] :: No SSL/TLS
:: [   FAIL   ] :: TLS (Expected 0, got 1)
:: [   FAIL   ] :: SSL (Expected 0, got 255)

Additional info:

As you can see from attached ldap.conf, TLS_CACERTDIR works fine with NSS DB, but TLSCACertificatePath does not (see slapd.conf). I am not sure that it is allowed to set this directive to NSS DB since slapd.conf(5) does not contain any details about using NSS DB. But according to the Admin Guide [1], it should work. 

[1] http://www.openldap.org/doc/admin24/tls.html

Created attachment 519629 [details]
proposed fix for manual pages

Attaching proposed patch. All changes are pulled from upstream.

The changes target only ldap.conf(5) and slapd-config(5), not obsoleted slapd.conf(5).

Fixed in openldap-2.4.23-18.el6

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
- always
- slapd-config(5) and ldap.conf(5) manual pages contain incorrect information about TLS settings
- upstream patch applied, which updates TLS documentation relevant for Mozilla NSS crypto library
- slapd-config(5) and ldap.conf(5) contain more accurate information about TLS settings

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, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHBA-2011-1514.html