Bug 1381379 - Merging subordinate CA and external CA installation
Summary: Merging subordinate CA and external CA installation
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: RHCS Maintainers
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-03 22:46 UTC by Matthew Harmsen
Modified: 2020-10-04 21:16 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-31 01:51:15 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Github dogtagpki pki issues 2611 0 None None None 2020-10-04 21:16:17 UTC

Description Matthew Harmsen 2016-10-03 22:46:47 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/pki/ticket/2491

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.
Comment 1 Matthew Harmsen 2016-10-04 20:45:41 UTC 
Per PKI Bug Council Meeting of 10/04/2016: 7.4
Note You need to log in before you can comment on or make changes to this bug.