When standing up a CA using pkispawn and attempting to use an HSM setting things like pki_ssl_server_token = dev-intca pki_subsystem_token = dev-intca
show up in the spawn log but when the install is complete a modutil -list -nocertdb -dbdir . still shows that its using the Internal NSS DB. I believe the part that is missing is what links the alias/ db to the HSM libraries during the install. This is mentioned in https://www.redhat.com/archives/pki-users/2014-November/msg00007.html and in the email below from cfu.
Email snippet... what's missing is the following: modutil -dbdir <instance dir>/alias -nocertdb -add lunasa -libfile /usr/safenet/lunaclient/lib/libCryptoki2_64.so for example modutil -dbdir /var/lib/pki/pki-tomcat/ca/alias -nocertdb -add lunasa -libfile /usr/safenet/lunaclient/lib/libCryptoki2_64.so
Somewhere in pkispawn after the instance is created but before it's configured it needs to do that.
You want to make the libfile a config parameter.
Checked in to 'master':
Add HSM options to pkispawn 20150413-Add-HSM-options-to-pkispawn.patch
Metadata Update from @dminnich: - Issue assigned to mharmsen - Issue set to the milestone: 10.2.3
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/1908
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.