Currently, the --cert <filename> option for pki-server subsystem-cert-update command hasn't been implemented. This command automates the importing of the certificate passed as argument into NSS database and overwrites the existing one. Also, necessary changes are made in the CS.cfg file.
--cert <filename>
pki-server subsystem-cert-update
CS.cfg
Reference: http://pki.fedoraproject.org/wiki/System_Certificate_Renewal#PKI_10.4_or_later_2
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: critical - Issue set to the milestone: 10.4
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.4)
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1466073
Fixed in master: * https://github.com/dogtagpki/pki/commit/d762073c4b5bcd4f9f30e3b8439983a497a77c97
Metadata Update from @edewata: - Issue assigned to dmoluguw - Issue set to the milestone: 10.4.9 (was: 10.5)
Metadata Update from @edewata: - Issue priority set to: major (was: critical)
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/2876
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.