From 00d7baffb31bdabc92c954b16050236a5ca29715 Mon Sep 17 00:00:00 2001 From: Jack Magne Date: Thu, 7 May 2015 15:38:47 -0700 Subject: Simple fix for this is not requiring the pki_client_database_password to be set when performing a clone operation. Tested with a cloned CA and a couple of other subysstems, such as OCSP. --- base/server/python/pki/server/deployment/pkihelper.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'base/server/python') diff --git a/base/server/python/pki/server/deployment/pkihelper.py b/base/server/python/pki/server/deployment/pkihelper.py index e6f001910..4a8398afc 100644 --- a/base/server/python/pki/server/deployment/pkihelper.py +++ b/base/server/python/pki/server/deployment/pkihelper.py @@ -563,7 +563,9 @@ class ConfigurationFile: if config.str2bool(self.mdict['pki_backup_keys']): self.confirm_data_exists("pki_backup_password") # Verify existence of Client Pin for NSS client security databases - self.confirm_data_exists("pki_client_database_password") + # if not a clone. + if not self.clone: + self.confirm_data_exists("pki_client_database_password") # Verify existence of Client PKCS #12 Password for Admin Cert self.confirm_data_exists("pki_client_pkcs12_password") # Verify existence of PKCS #12 Password (ONLY for Clones) -- cgit