During testing, it was discovered that when creating a clone on an HSM, we still require transportation of the 'master' NSS db software certificates to the 'clone' NSS db in order to provide the proper Trust attributes to the certificates on the HSM.
IMPORTANT: These software certificates are only used to establish the trust flags on the certificates that are actually stored on the HSM; all private keys are stored on the HSM.
Proposed Milestone: 10.2.5
Sample workaround 1 for a CA using 'certutil': ``` MASTER:
# cd /var/lib/pki/pki-tomcat/alias # certutil -d . -n "caSigningCert cert-pki-tomcat CA" -L -a > casign.crt # certutil -d . -n "auditSigningCert cert-pki-tomcat CA" -L -a > caaudit.crt
CLONE:
# cd /var/lib/pki/pki-tomcat/alias Copy 'casign.crt' and caaudit.crt' from the 'master' to this directory. # certutil -A -d . -n "caSigningCert cert-pki-tomcat CA" -t "CTu,CTu,CTu" -a -i casign.crt # certutil -A -d . -n "auditSigningCert cert-pki-tomcat CA" -t "u,u,Pu" -a -i caaudit.crt # systemctl restart pki-tomcatd@pki-tomcat.service
Sample alternative workaround 2 for a CA using 'certutil':
CLONE: # cd /var/lib/pki/pki-tomcat/alias # certutil -d . -n "dev-intca:caSigningCert cert-pki-tomcat CA" -t "CTu,CTu,CTu" -h dev-intca -M Enter Password or Pin for "dev-intca": # certutil -d . -n "dev-intca:auditSigningCert cert-pki-tomcat CA" -t "u,u,Pu" -h dev-intca -M Enter Password or Pin for "dev-intca": # systemctl restart pki-tomcatd@pki-tomcat.service
Could pki_backup_keys be used to accomplish the needed? Seems like we had to not specify that to use an hsm though.
Per IRC conversation, vakwetu volunteered to create the patch if mharmsen would test it.
Fix for HSM cloning issue (vakwetu + minor changes from mharmsen) 20150616-Fix-for-HSM-cloning-issue.patch
Successfully tested on master-clone LunaSA setup.
Checked into 'master':
Metadata Update from @mharmsen: - Issue assigned to vakwetu - Issue set to the milestone: 10.2.5
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/1964
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.