There should be a CLI to export the certificate chain from CA (e.g. pki ca-cert-chain-export).
How reproducible:
always
Steps to Reproduce:
1. pkispawn of an externally signed certificate requires the certificate chain of the certificate for the parameter pki_external_ca_cert_chain_path
Actual results:
None of the current CLI returns the certificate chain from CA in a single step.
Expected results:
CLI to export the certificate chain from CA in a single step.
Per CS/DS Meeting of 03/09/2015: 10.3
NOTE: Marking as 'minor' since UI can be used as a workaround for this issue.
Per Bug Triage of 05/03/2016: 10.4
Metadata Update from @mharmsen: - 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.5 (was: UNTRIAGED)
Metadata Update from @mharmsen: - Issue priority set to: major (was: minor)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
This is important to reduce dependency from the UI. Some people have been asking for this feature.
Metadata Update from @edewata: - Issue priority set to: critical (was: major)
Per 10.5.x/10.6 Triage: 10.5.x
alee: seems like a useful addition to the cli, while making installation easier.
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.6)
Metadata Update from @mharmsen: - Issue priority set to: major (was: critical)
Metadata Update from @cipherboy: - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
Duplicate of https://pagure.io/dogtagpki/issue/3117
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/1863
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.