Clone CA: Client database directory password required for install

[pki-bot]

This issue was migrated from Pagure Issue #1266. Originally filed by mharmsen (@mharmsen) on 2015-02-25 01:14:16:

• Closed as Fixed
• Assigned to jmagne (@jmagne)
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1165864

---

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

[pki-bot]

Comment from mharmsen (@mharmsen) at 2015-02-27 01:50:00

Per 10.2.3 Triage meeting of 02/26/2015: 10.2.3

[pki-bot]

Comment from jmagne (@jmagne) at 2015-05-08 00:48:03

Patch submitted for review.

[pki-bot]

Comment from jmagne (@jmagne) at 2015-05-08 02:14:29

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
00d7baf master -> master

[pki-bot]

Comment from jmagne (@jmagne) at 2015-05-08 02:15:13

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.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-02-27 14:03:12

Metadata Update from @mharmsen:

• Issue assigned to jmagne
• Issue set to the milestone: 10.2.4