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.
DescriptionThorsten Scherf
2019-05-15 07:22:33 UTC
Description of problem:
Setup: Externally signed IdM CA certificate. The external CA certificate is renewed at some point, so that the IdM CA certificate also needs to be renewed:
# ipa-cacert-manage renew --external-ca
# ipa-cacert-manage renew --external-cert-file=/root/ipa-new.crt --external-cert-file=/root/ipa-ca-new.crt
Certmonger shows that the 'caSigningCert' has been renewed successfully. Running the following 'certmonger' command still writes the old IdM CA certificate into '/tmp/foo.crt' though:
# ipa-getcert request -f /tmp/foo.pem -k /tmp/foo.key -F /tmp/foo.crt
Reason for this is that the LDAP entry 'cn=cacert,cn=ipa,cn=etc,$SUFFIX' is not updated with the new IdM CA certificate. A manual update of this entry resolves the problem.
Version-Release number of selected component (if applicable):
ipa-server-4.6.4-10.el7.x86_64
certmonger-0.78.4-10.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. see above
2.
3.
Actual results:
Executing 'ipa-getcert request' uses the old IdM CA certificate.
Expected results:
Executing 'ipa-getcert request' should use the renewed IdM CA certificate.
Additional info:
Comment 2Florence Blanc-Renaud
2019-05-15 09:11:06 UTC