#2491 [RFE] Merging subordinate CA and external CA installation
Closed: migrated by dmoluguw. Opened by edewata.

Dogtag supports the following installation cases:

  • subordinate CA (1 step)
  • external CA (2 steps)

In the subordinate CA case, the new CA has an option whether to join the existing security domain or to create a new security domain.

In the external CA case, if the parent CA is Dogtag, the new CA should have the same option as well.

To reduce code maintenance, it might be possible to merge the code for these cases. The subordinate CA install would be an automated 1-step process, while the external CA install would be a manual 2-step process. The difference is whether to sign the CSR automatically or manually.


Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1381379

Per PKI Bug Council Meeting of 10/04/2016: 10.4

Metadata Update from @edewata:
- Issue set to the milestone: UNTRIAGED

Metadata Update from @mharmsen:
- 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: 10.4 (was: UNTRIAGED)

Metadata Update from @edewata:
- 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/2611

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

Metadata