pkispawn CA fails when the system is in FIPS mode.
Steps to Reproduce:
1. x86_64 system is enabled with FIPS. 2. pkispawn CA using 2 step install process (with hsm). a. First step of pkispawn with pki_skip_configuration=True succeeds. b. Apply the fips ssl ciphers as described in http://pki.fedoraproject.org/wiki/SSL and pkispawn with pki_skip_installation=True. 3. pkispawn hangs.
Actual results:
'pki_user': 'pkiuser', 'pki_user_deployment_cfg': 'ca_inst.inf', 'pki_user_deployment_cfg_replica': '/etc/sysconfig/pki/tomcat/dogtag-CA-pkiuser-non-tms/ca/deployment.cfg', 'pki_user_deployment_cfg_spawn_archive': '/var/log/pki/dogtag-CA-pkiuser-non-tms/ca/archive/spawn_deployment.cfg.20171117140524', 'resteasy_lib': u'/usr/share/java/resteasy-base', 'sensitive_parameters': '\npki_admin_password\npki_backup_password\npki_client_database_password\npki_client_pin\npki_client_pkcs12_password\npki_clone_pkcs12_password\npki_ds_password\npki_external_pkcs12_password\npki_pkcs12_password\npki_one_time_pin\npki_pin\npki_replication_password\npki_security_domain_password\npki_server_pkcs12_password\npki_token_password', 'spawn_scriplets': '\ninitialization\ninfrastructure_layout\ninstance_layout\nsubsystem_layout\nwebapp_deployment\nslot_substitution\nsecurity_databases\nselinux_setup\nconfiguration\nfinalization'} pkispawn hung at this point. No useful info in the pkispawn logs for the failure.
Expected results:
pkispawn should be successful.
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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1514579 - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @mharmsen: - Issue assigned to jmagne
The issue got resolved with a new build of openssl which resolved a regression.
Metadata Update from @mharmsen: - Issue close_status updated to: invalid - Issue set to the milestone: 10.5.3 (was: 10.5) - 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/2983
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.