-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
rhel-8.6.0
-
None
-
Important
-
rhel-idm-cs
-
ssg_idm
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
All
-
None
-
57,005
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:
- external trackers