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.
This bug is created as a clone of upstream ticket:
https://pagure.io/freeipa/issue/8223
### Issue
Expired CA's can be returned by certstore.get_ca_certs().
This in turn breaks all the tools (ldapsearch / ipa-join / ipa-certupdate / etc) that require the first cert in ca.crt to be valid.
Summarizing the options (and quoting Fraser):
There are a few options (not all mutually exclusive).
* Backport our intended ipa-certupdate changes to earlier releases and affected customers would have to update the clients.
* Move expired CA certs to an "attic" when we run ipa-cacert-manage. If we do this, a "housekeeping" subcommand is warranted, e.g. to move aside expired certs (or if the customer is doing time-travel, to bring valid certs out of the attic).
* Implement "get trusted certs" as an IPA-API command (with accompanying change to ipa-certupdate, but probably not one to backport). That way, if we ever need to change the ordering heuristics again, only the servers need to be updated (assuming client is at a verison that uses the API instead of pulling certs directly from LDAP).
* ipa-cacert-manage learns how to remove specific certificates only (not all certs for a given subject). I think I prefer the attic idea though.
As this method cannot be changed for older clients and is part of the enrollment (ipa-client-install), the options that remains are #2 (attic) and #4 (prune).
This needs to be done to allow the cert-renewal process to still be able to track older certs (for verification purposes) but not be a part of a certificate chain that can potentially break other certificate management tools. Allowing old certs to be retained, without breaking any processes.
Comment 5RHEL Program Management
2021-09-13 07:26:57 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.