Currently migration is done using the "existing CA" installation with some additional manual tasks:
Basically, after the "existing CA" installation there are some migration-specific tasks that need to be done including (and not limited to):
To simplify the migration process, a new pkispawn parameter (e.g. pki_migration) could be added to be used instead of the pki_existing parameter. When this parameter is specified, it will execute at least some of the above tasks automatically. The automation can be added incrementally depending on the priority.
Per PKI Bug Council of 08/31/2016: 10.4 critical
Metadata Update from @edewata: - Issue set to the milestone: 10.4
Metadata Update from @edewata: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue set to the milestone: FUTURE (was: 10.4)
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/2562
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)