Bug 1935925
| Summary: | ipa-cert-fix fails and leave the temp CA SSL server cert in place, making recovery more difficult when certmonger failed to renew IPA internal certs | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Marc Sauton <msauton> |
| Component: | pki-core | Assignee: | RHCS Maintainers <rhcs-maint> |
| Status: | CLOSED MIGRATED | QA Contact: | idm-cs-qe-bugs |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.6 | CC: | ckelley, mharmsen, mrhodes, rcritten, skhandel, tscherf, vvanhaft |
| Target Milestone: | beta | Keywords: | MigratedToJIRA, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-19 12:57:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Per meeting of June 30, 2021 -- deferring this fix (which may not be simple) to RHCS 10.4/RHEL 8.6 for now. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |
Description of problem: ipa-cert-fix relies on pki-server cert-fix , so this report's component may need to be set from ipa to pki-core. but: ipa-cert-fix fails and leave the temp CA SSL server cert in place, making recovery more difficult when certmonger failed to renew IPA internal certs. certmonger failed to renew the IPA internal certificates. some systems may have bee updated with RHEL-7.9 customer uses ipa-cert-fix which failed. then try to set system back in time just before some of the CA's certs are till valid, to run some getcert resubmit, which also failed on reaching the CA's HTTPS service. the reason in this case, is the IPA CA's SSL server cert was left with the temporary cert of 3 month validity date in Q1 2021 last time ipa-cert-fix failed, and with same serial as the original cert (not X.509 "correct") , so going back in time to try renew the other expired cert cannot work as the SSL server cert is not yet valid. there is no clear way to recover the real original CA SSL server cert ( was serial 3) the cert-fix tools in ipa and dogtag seem to assume there is no error, so there is no recovery mechanism: ./base/server/python/pki/server/cli/cert.py ... instance.cert_del('sslserver') at this point, the result in case of ipa-cert-fix failure is a more difficult situation to solve. I suupose the private was not removed as the default in cert_del is with remove_key=False , so there may be a way to recover the original expired cert if it is till available in the LDAP backend: ldapsearch -o ldif-wrap=no -xLLLD "cn=directory manager" -W -s sub -b ou=certificateRepository,ou=ca,o=ipaca serialno=013 Version-Release number of selected component (if applicable): RHEL-7.9 How reproducible: N/A Steps to Reproduce: 1.N/A 2. 3. Actual results: Expected results: Additional info: