#944 RFE Request to query or manage CRL using pki command
Closed: migrated 3 years ago by dmoluguw. Opened 10 years ago by mrniranjan.

Currently there is method to query or Manage CRL's using pki command. Requesting feature to add this functionality to pki command.


Adding more information as to what specifically QE is looking at:

  1. We would like to have a way to publish CRL's immediately, currently we cannot modify the publishing related information from command line
  2. Modify the publishing schedule through command line
  3. currently when we revoke a cert with a reason, we cannot verify through command line to check if the cert was revoked with reason we wanted to revoke, so we would like to have command line interface to query crl to see if the certs that are on crl list have the right revocation reason/
  4. Query the CRL list by certificate reasons, etc.

Per CS/DS meeting of 4/7/2014, it was determined that this ticket would be filed for the 10.3 milestone.

Per Bug Triage of 05/05/2016: 10.4

Metadata Update from @mrniranjan:
- Issue set to the milestone: UNTRIAGED

7 years ago

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: FUTURE (was: UNTRIAGED)

6 years ago

Per 10.5.x/10.6 Triage: FUTURE

mharmsen: re-working CRLs will probably not be attempted until 10.6 or later

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/1510

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

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)

3 years ago

Login to comment on this ticket.

Metadata