#2784 Adding CMCResponse option to export ASCII PKCS #7 file.
Closed: fixed Opened by edewata.

The CMCResponse tool currently displays the resulting cert chain to screen. There should be an option to export the cert chain into an ASCII PKCS #7 file for further processing (e.g. installing sub CA).

Also, if the CMC response is an error, the CMCResponse should exit with a non-zero code.


Fixed in master:

  • https://github.com/dogtagpki/pki/commit/cbd8a773b7b6ce8dc099dacb3e765a1823c83153
  • https://github.com/dogtagpki/pki/commit/2a7c46faa8c6f7cae0c06b5ef2c12f1d5a7a2d00

Metadata Update from @edewata:
- 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 type adjusted to None
- Custom field version adjusted to None

Metadata Update from @mharmsen:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue close_status updated to: fixed
- Issue priority set to: critical
- Issue set to the milestone: 10.5 (was: 0.0 NEEDS_TRIAGE)
- Issue status updated to: Closed (was: Open)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.0 (was: 10.5)

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.0-1.fc27

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

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