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.
.Added a new message to help set up `nsSSLPersonalitySSL`
Previously, many times happened that RHDS instance failed to start if the TLS certificate nickname didn't match the value of the configuration parameter `nsSSLPersonalitySSL`. This mismatch happened when customer copy the NSS DB from a previous instance or export the certificate's data but forget to set the `nsSSLPersonalitySSL` value accordingly. With this update, you can see log an additional message which should help a user to set up `nsSSLPersonalitySSL` correctly.
Description of problem:
RHDS instance will fail to start if the TLS server certificate nickname doesn't match the value
of the configuration parameter "nsSSLPersonalitySSL".
The mismatch typically happens when customers copy the NSS DB from a previous instance
or export the certificates data but forget to set the "nsSSLPersonalitySSL" value accordingly.
Version-Release number of selected component (if applicable):
# rpm -qa | grep 389-ds-base
389-ds-base-debugsource-1.4.2.12-2.module+el8dsrv+6428+6e54c518.x86_64
389-ds-base-1.4.2.12-3.module+el8dsrv+6923+6ab1d5c5.x86_64
389-ds-base-debuginfo-1.4.2.12-2.module+el8dsrv+6428+6e54c518.x86_64
389-ds-base-libs-1.4.2.12-3.module+el8dsrv+6923+6ab1d5c5.x86_64
#
# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.2 (Ootpa)
#
How reproducible:
Always.
Steps to Reproduce:
1. Get the certificate nickname:
# certutil -d /etc/dirsrv/slapd-<INSTANCE>/ -L
Certificate Nickname Trust Attributes
SSL,S/MIME,JAR/XPI
Self-Signed-CA CT,,
Server-Cert u,u,u
#
2. Stop the RHDS instance and set nsSSLPersonalitySSL to a value different of the actual nickname
# grep -i nsSSLPersonalitySSL /etc/dirsrv/slapd-<INSTANCE>/dse.ldif
nsSSLPersonalitySSL: otherNickname
#
3. Try to start the instance
Actual results:
The startup fails with the following messages in the errors log:
[06/Nov/2020:18:37:03.873591352 +0100] - ERR - attrcrypt_fetch_private_key - Can't find certificate otherNickname: -5950 - File not found.
[06/Nov/2020:18:37:03.875333480 +0100] - ERR - attrcrypt_fetch_private_key - Can't get private key from cert otherNickname: -5950 - File not found.
...
[06/Nov/2020:18:37:03.878800070 +0100] - ERR - attrcrypt_fetch_private_key - Can't find certificate otherNickname: -5950 - File not found.
[06/Nov/2020:18:37:03.880365271 +0100] - ERR - attrcrypt_fetch_private_key - Can't get private key from cert otherNickname: -5950 - File not found.
Expected results:
It would be nice to log an additional message stating to check if the nickname indeed matches the nsSSLPersonalitySSL.
Additional info:
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-2021:4203
Description of problem: RHDS instance will fail to start if the TLS server certificate nickname doesn't match the value of the configuration parameter "nsSSLPersonalitySSL". The mismatch typically happens when customers copy the NSS DB from a previous instance or export the certificates data but forget to set the "nsSSLPersonalitySSL" value accordingly. Version-Release number of selected component (if applicable): # rpm -qa | grep 389-ds-base 389-ds-base-debugsource-1.4.2.12-2.module+el8dsrv+6428+6e54c518.x86_64 389-ds-base-1.4.2.12-3.module+el8dsrv+6923+6ab1d5c5.x86_64 389-ds-base-debuginfo-1.4.2.12-2.module+el8dsrv+6428+6e54c518.x86_64 389-ds-base-libs-1.4.2.12-3.module+el8dsrv+6923+6ab1d5c5.x86_64 # # cat /etc/redhat-release Red Hat Enterprise Linux release 8.2 (Ootpa) # How reproducible: Always. Steps to Reproduce: 1. Get the certificate nickname: # certutil -d /etc/dirsrv/slapd-<INSTANCE>/ -L Certificate Nickname Trust Attributes SSL,S/MIME,JAR/XPI Self-Signed-CA CT,, Server-Cert u,u,u # 2. Stop the RHDS instance and set nsSSLPersonalitySSL to a value different of the actual nickname # grep -i nsSSLPersonalitySSL /etc/dirsrv/slapd-<INSTANCE>/dse.ldif nsSSLPersonalitySSL: otherNickname # 3. Try to start the instance Actual results: The startup fails with the following messages in the errors log: [06/Nov/2020:18:37:03.873591352 +0100] - ERR - attrcrypt_fetch_private_key - Can't find certificate otherNickname: -5950 - File not found. [06/Nov/2020:18:37:03.875333480 +0100] - ERR - attrcrypt_fetch_private_key - Can't get private key from cert otherNickname: -5950 - File not found. ... [06/Nov/2020:18:37:03.878800070 +0100] - ERR - attrcrypt_fetch_private_key - Can't find certificate otherNickname: -5950 - File not found. [06/Nov/2020:18:37:03.880365271 +0100] - ERR - attrcrypt_fetch_private_key - Can't get private key from cert otherNickname: -5950 - File not found. Expected results: It would be nice to log an additional message stating to check if the nickname indeed matches the nsSSLPersonalitySSL. Additional info: