CA installation with HSM prompts for HSM password during silent installation
Steps to Reproduce:
1. cat /tmp/ca.cfg [DEFAULT] pki_instance_name = pki-ca-June22 pki_token_password = Secret123 pki_admin_password = Secret123 pki_hostname = localhost pki_security_domain_name = pki-ca-June22.org pki_security_domain_password = Secret123 pki_client_dir = /opt/pki-ca-June22 pki_client_pkcs12_password = Secret123 pki_ds_password = Secret123 pki_ds_ldap_port = 389 pki_hsm_enable=True pki_hsm_libfile=/opt/nfast/toolkits/pkcs11/libcknfast.so pki_hsm_modulename=nfast pki_token_name=NHSM6000 pki_token_password=redhat123 pki_audit_signing_token=NHSM6000 pki_subsystem_token=NHSM6000 pki_ssl_server_token=NHSM6000 [CA] pki_import_admin_cert = False pki_ds_hostname = localhost pki_admin_nickname = PKI CA Administrator for Example.Org pki_ca_signing_token=NHSM6000 pki_ocsp_signing_token=NHSM6000 2. pkispawn -s CA -f /tmp/ca.cfg
Actual results:
[root@nocp4 ~]# pkispawn -s CA -f /tmp/ca.cfg Log file: /var/log/pki/pki-ca-spawn.20160623094647.log Loading deployment configuration from /tmp/ca.cfg. Installing CA into /var/lib/pki/pki-ca-June22-2. Storing deployment configuration into /etc/sysconfig/pki/tomcat/pki-ca-June22-2/ca/deployment.cfg. Module "nfast" added to database. Enter password for NHSM6000:
Expected results:
Should take the password from pki_token_password=redhat123 in the cfg file
Per PKI Bug Council of 06/23/2016: 10.3.4
Fixed in master:
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1350446 (Red Hat Enterprise Linux 7)
Metadata Update from @rpattath: - Issue assigned to edewata - Issue set to the milestone: 10.3.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/2504
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.