SUBCA config file
newsubca

CA configuration file
newca

CA Spawn log
caspawn

In the spawn log it says that sec domain is existing when I configured it to form a new security domain. Also, issuing_ca is right but issuing_ca_hostname and https_port are taken as the subca's hostname and port rather than the master CAs

OK - this is a bug.

The problem occurs when you try to create a subCA with its own security domain.

See the following code in pkiparser.py:

            elif config.pki_subsystem != "CA" or\
                config.str2bool(self.mdict['pki_clone']) or\
                config.str2bool(self.mdict['pki_subordinate']):
            # PKI KRA, PKI OCSP, PKI RA, PKI TKS, PKI TPS,
            # CA Clone, KRA Clone, OCSP Clone, TKS Clone, TPS Clone, or
            # Subordinate CA
            self.mdict['pki_security_domain_type'] = "existing"
            self.mdict['pki_security_domain_uri'] = \
                "https" + "://" + \
                self.mdict['pki_security_domain_hostname'] + ":" + \
                self.mdict['pki_security_domain_https_port']

Basically, if its subordinate, then it always returns "existing".

Moving to 10.2.1.

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

fixed. pushed to master.

To ssh://vakwetu@git.fedorahosted.org/git/pki.git
67f8c07..b644429 master -> master

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

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.