Bug 1436657

Summary: Add workaround for pki_pin for FIPS
Product: Red Hat Enterprise Linux 7 Reporter: Petr Vobornik <pvoborni>
Component: ipaAssignee: IPA Maintainers <ipa-maint>
Status: CLOSED ERRATA QA Contact: Abhijeet Kasurde <akasurde>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: akasurde, enewland, nsoman, pvoborni, rcritten, tkrizek, tscherf
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-4.5.0-3.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 09:46:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1125174    

Description Petr Vobornik 2017-03-28 11:58:52 UTC 
Cloned from upstream: https://pagure.io/freeipa/issue/6824

Dogtag is unable to create a strong-enough PIN in FIPS (https://pagure.io/dogtagpki/issue/2556 - they only use some numbers) to be used to create an NSS database.
Add a workaround setting `pki_pin` to a random value we can generate by ipautil.ipa_generate_password().
Comment 2 Petr Vobornik 2017-03-28 11:59:09 UTC 
Upstream ticket:
https://pagure.io/freeipa/issue/6824
Comment 3 Tomas Krizek 2017-03-28 15:08:44 UTC 
Fixed upstream
ipa-4-5:
https://pagure.io/freeipa/c/39eac72faef5f44c9fb2cad943ad58d23fe60cf3
master:
https://pagure.io/freeipa/c/e204d030fc4154800acb0b2b312188e72dd80f80
Comment 5 Abhijeet Kasurde 2017-05-29 11:34:52 UTC 
Verified using IPA version :: 
# rpm -qa ipa-server
ipa-server-4.5.0-13.el7.x86_64

[root@ipaserver01 ~]# grep pki_pin /var/log/ipaserver-install.log && echo $?
pki_pin = XXXXXXXX
0

Marking BZ as verified. Also, ran Sanity and FIPS related testcases to verify PKI_PIN.
Comment 6 errata-xmlrpc 2017-08-01 09:46:16 UTC 
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:2304