Clone CA imports the admin cert of the Root CA and the client database directory is used to store the caadmincert temporarily for the creation of admincert p12 file in a ROOT CA, hence for clone CA we should not require the client databse directory password but this is a parameter without which the clone CA install fails.
Steps to Reproduce:
1.Create a root ca 2.create its clone ca using pkispawn without passing the parameter pki_client_database_password, the clone CA install will fail
Actual results:
Clone CA install failing
Expected results:
Clone CA should not fail
Per 10.2.3 Triage meeting of 02/26/2015: 10.2.3
Patch submitted for review.
Patch approved, checked in, closing:
Counting objects: 9, done. Delta compression using up to 8 threads. Compressing objects: 100% (7/7), done. Writing objects: 100% (9/9), 795 bytes | 0 bytes/s, done. Total 9 (delta 6), reused 0 (delta 0) To ssh://git.fedorahosted.org/git/pki.git 00d7baffb31bdabc92c954b16050236a5ca29715 master -> master
Test fix by simply NOT setting the specified entry in the deployment.cfg file, when creating a clone. The clone should happen without an issue.
Metadata Update from @mharmsen: - Issue assigned to jmagne - Issue set to the milestone: 10.2.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/1828
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.
Login to comment on this ticket.