-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MasterCRL does not immediatetly publish a new Full CRL when clone CA revokes a certificate. #5011
Comments
Have you configured like in this workflow: https://github.com/dogtagpki/pki/blob/master/.github/workflows/ca-crl-test.yml#L76 |
These are all the settings on the Master CA related to CRL:
I've updated the |
After the interval or with the update service does get CRL updated? |
Yes, in those cases the CRL does get updated. |
In this case the problem seems more related to configuration but to be verified |
Summary:
MasterCRL does not immediatetly publish a new Full CRL when clone CA revokes a certificate.
Build:
idm-pki-ca-11.5.1-1.el9.noarch, AlmaLinux 9
Steps to reproduce:
Install pki-ca on a master and a clone instance
Spawn master and then spawn clone, using default settings.
Configure on the CA Master:
ca.crl.MasterCRL.alwaysUpdate=true
ca.listenToCloneModifications=true
And restart the CA instance.
Revoke a certificate on the Clone CA.
Expected Result:
The Master CA processes the certificate status changes, and immediately publishes a new Full CRL.
Actual Result:
The Master CA processes the certificate status changes but does not immediately publish a new Full CRL.
Logs from the Master CA when revocation happens on the Clone, shows that the Certificate status does get updated. However no immediate CRL publishing is done.
If this is indeed a bug and not working as intended, I wouldn't mind opening a PR for this.
The text was updated successfully, but these errors were encountered: