Executing 'pkispawn -s CA -f /root/ca-hsm.cfg -v' with 'pki_audit_signing_nickname' and it is ignored in installation.
$ certutil -L -d /var/lib/pki/pki-tomcat/alias -h all -f password.txt Certificate Nickname Trust Attributes SSL,S/MIME,JAR/XPI pki-tomcat/sslserver/fedora28.magnuskkarlsson.local u,u,u auditSigningCert cert-pki-tomcat CA u,u,Pu pki-tomcat/ca_signing CTu,Cu,Cu HSM:pki-tomcat/ca_signing CTu,Cu,Cu HSM:auditSigningCert cert-pki-tomcat CA u,u,Pu HSM:pki-tomcat/subsystem u,u,u HSM:pki-tomcat/ocsp_signing u,u,u $ certutil -K -d /var/lib/pki/pki-tomcat/alias -h all -f password.txt certutil: Checking token "NSS Generic Crypto Services" in slot "NSS Internal Cryptographic Services" certutil: no keys found certutil: Checking token "NSS Certificate DB" in slot "NSS User Private Key and Certificate Services" < 0> rsa c4aa127997821ef8cc1db62659a6332b2d74bb96 NSS Certificate DB:pki-tomcat/sslserver/fedora28.magnuskkarlsson.local certutil: Checking token "HSM" in slot "SoftHSM slot ID 0x7b28a2c3" < 0> rsa 8ed61479fd2d9af27e72c01622a409941df82389 pki-tomcat/ca_signing < 1> rsa 5d8908fec56c2e969a8af18a26073d9bcdeaf43c auditSigningCert cert-pki-tomcat CA < 2> rsa a187aa2713ccc1ea7405cee9053778360851ac51 pki-tomcat/ocsp_signing < 3> rsa 1a9341bfa4973506ab8375515f5ef3b38c553662 pki-tomcat/subsystem
<!!image>
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Here is a working example on PKI 10.6: https://github.com/dogtagpki/pki/blob/master/base/server/docs/installation/Installing_CA_with_HSM.md
Metadata Update from @magnuskkarlsson: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/3164
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.