Red Hat Bugzilla – Bug 1400149
pkispawn fails to create CA subsystem on FIPS enabled system
Last modified: 2017-08-01 18:48:25 EDT
Created attachment 1226356 [details] Failing pkispawn configuration Description of problem: Running pkispawn -s CA with the config file from the attachment ends up in pkispawn error. Version-Release number of selected component (if applicable): pki-base-10.3.3-14.el7_3 How reproducible: Always Steps to Reproduce: 1. Setup your system for FIPS 2. run pkispawn with the given config (you can run ipa-server-install to make it easier for you) Actual results: CA subsystem installation fails. Expected results: CA subsystem installation succeeds. Additional info: From what I've gathered, the trouble is with generating 'pki_pin', which is then stored to 'pki_shared_pfile' which is used to access the /etc/pki/pki-tomcat/alias NSS database. However, 'pki_pin' is just a number and NSS databases in FIPS mode require at least one non-alphanumeric character.
Upstream ticket: https://fedorahosted.org/pki/ticket/2556
Fixed in master: * 9e3551fdb2c8d1f1bd7ad57249752c8ad6aece32
Tested on: pki-ca-10.4.1-6.el7.noarch kra-clone-prepare fails if the password have "=" in password.conf password.conf: #internal=YoYEw1lgY6'4 internal=Z?t9:f/0B%+= internaldb=Secret123 replicationdb=1156996686
The kra-clone-prepare calls pki CLI which reads the password.conf to export KRA certificates and keys from the NSS database into a PKCS #12 file. The problem is the pki CLI treats the "=" in the file as delimiter for token name and password, so the password is parsed incorrectly. One possible solution is to provide separate pki CLI parameters for a password file containing just a single password (without token name), and for a password.conf which may contain multiple token names and passwords.
Another possibility is not to use equal sign in random passwords.
Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Excluded equal sign from random password: * https://github.com/dogtagpki/pki/commit/03235ab51d102ba722e71adf00d2f721c77cd222
Tested in version: pki-server-10.4.1-9.el7.noarch RHCS subsystems CA, KRA, OCSP, TKS and TPS installed successfully on a FIPS and non-FIPS RHEL 7.4 systems with the auto generated FIPS compliant passwords. Sanity tests looks good for each subsystem. Marking the bug verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2110