dogtagpki

#853 Missing instruction to import system certs for cloning
Closed: Fixed Opened by edewata.

Closed: Fixed
Reopen Issue

Once the PKCS #12 containing the system certificates is obtained from the server (see ticket #852), the file should be placed securely on the replica machine such that it can be imported by the CA clone. The manual page for pkispawn should mention the following:

  • the recommended location to put the PKCS #12 file
  • the sample command to create the Dogtag user (e.g. pkiuser)
  • the sample command to set the file permission
  • the sample command to set the SE Linux context

[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/1420

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
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.