Requesting to show certificate serial Number that has been revoked in the output of cert-request-find --type revocation --status complete.
pki -d /opt/rhqa_pki/certs_db -n "CA_agentV" -c redhat123 cert-request-find --type revocation --status complete ----------------- 5 entries matched ----------------- Request ID: 15 Type: revocation Request Status: complete Operation Result: success Request ID: 19 Type: revocation Request Status: complete Operation Result: success Request ID: 417 Type: revocation Request Status: complete Operation Result: success Request ID: 431 Type: revocation Request Status: complete Operation Result: success Request ID: 445 Type: revocation Request Status: complete Operation Result: success
Currently in the above output I cannot see the certificate serialNumber which have been revoked. So one cannot tell Request ID 445 was assigned to revoke which certificate.
certificate serialnumber is displayed in the case of Completed enrollment requests
[root@dhcp207-176 dogtag]# pki -d /opt/rhqa_pki/certs_db -n "CA_agentV" -c redhat123 cert-request-find --type enrollment --status complete --size 3 ------------------- 215 entries matched ------------------- Request ID: 1 Type: enrollment Request Status: complete Operation Result: success Certificate ID: 0x1 Request ID: 2 Type: enrollment Request Status: complete Operation Result: success Certificate ID: 0x2
As we can see above completed enrollment requests also display serialNumber, Requesting to show certificate serialnumber even for completed Revocation requests.
proposed Milestone - 10.2.2
Per CS/DS meeting of 07/21/2014, proposed Milestone - 10.3.
Per Bug Triage of 05/05/2016: 10.3.1
attachment pki-ftweedal-0115-Include-serial-of-revoked-cert-in-CertRequestInfo.patch
Pushed to master (9bcc0bba57003a26ee0488def88a57ca883d9134)
Metadata Update from @mrniranjan: - Issue assigned to ftweedal - Issue set to the milestone: 10.3.2
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/1636
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.
Login to comment on this ticket.