dogtagpki

#852 Missing instruction to export system certs for cloning
Closed: Fixed Opened by edewata.

Closed: Fixed
Reopen Issue

In order to setup a CA clone, the CA master should have been created with the following parameters to backup the system certificates into a PKCS #12 file:

pki_backup_keys=True
pki_backup_password=<password>

If the CA wasn't created with these parameters, the system certificates can still be exported from the security database. The manual page for pkispawn should describe the backup parameters and the steps to export the system certificates.

Also, as a possible improvement, an additional parameter can be added to specify the backup location (e.g. pki_backup_path) which currently defaults to /etc/pki/pki-tomcat/alias/ca_backup_keys.p12.

[06/04/2014] - Moving to Milestone 10.2.1 due to schedule restrictions.

Proposed Milestone: 10.2.3 (per CS Meeting of 09/17/2014)

man page (complete earlier if possible)

Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog

Metadata Update from @edewata:
- Issue assigned to vakwetu
- Issue set to the milestone: 10.2 Backlog

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

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
None
None
None
Normal
defect
Documentation
Installer Cleanup/ Improvement
None
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.