I am trying to do CRL autoupdate from CA's CS.cfg bt setting ca.crl.test_crl.autoUpdateInterval=1 but it is not reflected on CA Agent page.
Steps to Reproduce:
1. I have a new issuing point test_crl added. 2. Config file is attached for CA . 3. I have revoked couple of certs.Now my CRL's are getting generated in every 1 minute like configured but revoked certs status is not getting updated. Issue 1: I have revoked few certificates now it should goto issuing points and gets updated. certs are getting updated with revocation data in LDAP.But with every CRL generation we don't see revoked certificates getting added. Workaround 1: Manually update them from CA Agent page. Issue 2: With the newly created issuing point test_crl, we tried to do a manual update it will not get updated . Workaround 2: To manually update always we have to set "clear CRL cache" then only it works while it is not needed for masterCRL.
Note: It would be helpful it we get a note about how CS.cfg properties for CRL works and a mapping of their functionality.
Additional info:
Sample CS.cfg attached to associated bug.
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1462291 - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: critical - Issue set to the milestone: 10.4
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.4)
Metadata Update from @mharmsen: - Issue priority set to: major (was: critical)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Per 10.5.x/10.6 Triage: 10.6
jmagne: uncertain whether or not this is a bug or a documentation issue
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2868
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.