Publishing CRL to LDAP directory fails when the LdapCRLRule predicate has isDeltaCRL set
Steps to Reproduce:
1. Create a publisher rule - rule1 2. rule 1 has type:crl, predicate:issuingPointId==MasterCRL && isDeltaCRL==false, mapper:LdapCrlMap, Publisher:LdapCrlPublisher 3. Enable Publishing and enable default LDAP publishing 4. Set Update CRL frequesncy to 1 minute 5. Issue a few certs of caUserCert profile 6. Revoke the certs 7. Either wait for a minute for the CRL to me updated or manually update the CRL from CA agent page. 8. In the CA agent page -> Update Directory Server -> Update the certificate revocation list to the directory. Click Update Directory
Actual results:
Error Message: The Certificate Revocation List could not be published in the directory - No rule instance matched for request CRL
Expected results:
CRL publishing should be successful
Additional info:
If the predicate of the rule is issuingPointId==MasterCRL then the publishing is successful and the directory has the entry for the CRL
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1105618 (Red Hat Certificate System)
Per CS/DS meeting of 11/02/2015: 10.4 - minor
Closed as WONT FIX for RHCS 8.x version of product.
Metadata Update from @rpattath: - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: None - Issue set to the milestone: 10.6 (was: UNTRIAGED)
Per 10.5.x/10.6 Triage: 10.6
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/2234
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)