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.
Description of problem:
The CA cert that is generated by dscreate won't import into a client's Shared System Certificates store.
Version-Release number of selected component (if applicable):
389-ds-base-1.4.1.3-7.module+el8.1.0+4150+5b8c2c1f.x86_64
How reproducible:
Install a 389 server, try to trust the Self-Signed-CA.pem
Steps to Reproduce:
1. dscreate from-file ...
2. trust anchor /etc/dirsrv/slapd-localhost/Self-Signed-CA.pem
3. trust list | head
Actual results:
pkcs11:id=%c3%0d%d0%4c%0a%cc%82%1f%1a%f4%75%94%35%16%0f%f6%27%34%9c%25;type=cert
type: certificate
label: ssca.389ds.example.com
trust: anchor
category: other-entry
Expected results:
pkcs11:id=%c3%0d%d0%4c%0a%cc%82%1f%1a%f4%75%94%35%16%0f%f6%27%34%9c%25;type=cert
type: certificate
label: ssca.389ds.example.com
trust: anchor
category: authority
Notice the category is incorrectly "other-entry"
Additional info:
openldap-client by default loads /etc/pki/tls/cert.pem which is a symlink to /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
Because the category is 'other-entry', when you run the command 'update-ca-trust' it won't add the certificate to /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
Note that update-ca-trust is simple shell script, the command that fails is:
DEST=/etc/pki/ca-trust/extracted
/usr/bin/p11-kit extract --format=pem-bundle --filter=ca-anchors --overwrite --comment --purpose server-auth $DEST/pem/tls-ca-bundle.pem
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:1.4 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/RHEA-2020:4695
Description of problem: The CA cert that is generated by dscreate won't import into a client's Shared System Certificates store. Version-Release number of selected component (if applicable): 389-ds-base-1.4.1.3-7.module+el8.1.0+4150+5b8c2c1f.x86_64 How reproducible: Install a 389 server, try to trust the Self-Signed-CA.pem Steps to Reproduce: 1. dscreate from-file ... 2. trust anchor /etc/dirsrv/slapd-localhost/Self-Signed-CA.pem 3. trust list | head Actual results: pkcs11:id=%c3%0d%d0%4c%0a%cc%82%1f%1a%f4%75%94%35%16%0f%f6%27%34%9c%25;type=cert type: certificate label: ssca.389ds.example.com trust: anchor category: other-entry Expected results: pkcs11:id=%c3%0d%d0%4c%0a%cc%82%1f%1a%f4%75%94%35%16%0f%f6%27%34%9c%25;type=cert type: certificate label: ssca.389ds.example.com trust: anchor category: authority Notice the category is incorrectly "other-entry" Additional info: openldap-client by default loads /etc/pki/tls/cert.pem which is a symlink to /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem Because the category is 'other-entry', when you run the command 'update-ca-trust' it won't add the certificate to /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem Note that update-ca-trust is simple shell script, the command that fails is: DEST=/etc/pki/ca-trust/extracted /usr/bin/p11-kit extract --format=pem-bundle --filter=ca-anchors --overwrite --comment --purpose server-auth $DEST/pem/tls-ca-bundle.pem