Currently pkispawn accepts PKCS #7 certificate chain (i.e. in pki_external_ca_cert_chain_path) for external CA and standalone KRA/OCSP cases. However, each system certificate (e.g. pki_external_ca_cert_path) still needs to be specified as a single certificate without chain.
In CMC case each system certificate will be returned as PKCS #7 data (see ticket #2784). The pkispawn should be modified to support PKCS #7 certificates directly. The certificate chain itself should become optional since it is already included in the PKCS #7 data.
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 type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @edewata: - Issue assigned to edewata
Metadata Update from @edewata: - Issue set to the milestone: 10.5 (was: 0.0 NEEDS_TRIAGE)
Fixed in master:
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue priority set to: critical - 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/2905
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.