To create certificate subsystem renew request, subsystem-cert-find cli missing the certificate serial number. It should be displayed.
Steps to Reproduce:
[root@pki1 ~]# pki-server subsystem-cert-find ca -i topology-02-CA ----------------- 5 entries matched ----------------- Cert ID: signing Nickname: caSigningCert cert-topology-02-CA CA Token: Internal Key Storage Token Cert ID: ocsp_signing Nickname: ocspSigningCert cert-topology-02-CA CA Token: Internal Key Storage Token Cert ID: sslserver Nickname: Server-Cert cert-topology-02-CA Token: Internal Key Storage Token Cert ID: subsystem Nickname: subsystemCert cert-topology-02-CA Token: Internal Key Storage Token Cert ID: audit_signing Nickname: auditSigningCert cert-topology-02-CA CA Token: Internal Key Storage Token
Documentation of the cli is not updated. http://www.dogtagpki.org/wiki/System_Certificate_Renewal
Actual results:
It did not show the serial no.
Expected results:
It should show the serial no.
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1566360 - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @mharmsen: - Issue close_status updated to: fixed - Issue set to the milestone: 10.6.0 (was: 10.6) - Issue status updated to: Closed (was: Open)
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/3119
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.