Bug 1447762
| Summary: | pkispawn fails occasionally with this failure ACCESS_SESSION_ESTABLISH_FAILURE | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Roshni <rpattath> | |
| Component: | pki-core | Assignee: | Endi Sukma Dewata <edewata> | |
| Status: | CLOSED ERRATA | QA Contact: | Asha Akkiangady <aakkiang> | |
| Severity: | urgent | Docs Contact: | Petr Bokoc <pbokoc> | |
| Priority: | urgent | |||
| Version: | 7.4 | CC: | arubin, dsirrine, edewata, mharmsen, msauton, pbokoc | |
| Target Milestone: | rc | Keywords: | Reopened, ZStream | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | pki-core-10.4.1-8.el7 | Doc Type: | Bug Fix | |
| Doc Text: |
"pkispawn" no longer generates invalid *NSS* database passwords
Prior to this update, "pkispawn" generated a random password for the *NSS* database which in some cases contained a backslash (`\`) character. This caused problems when *NSS* established *SSL* connections, which in turn caused the installation to fail with a `ACCESS_SESSION_ESTABLISH_FAILURE` error.
This update ensures that the randomly generated password can not contain the backslash character and a connection can always be established, allowing the installation to finish successfully.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1462973 1463358 (view as bug list) | Environment: | ||
| Last Closed: | 2017-08-01 22:50:57 UTC | Type: | Bug | |
| 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: | 1463358 | |||
|
Description
Roshni
2017-05-03 18:25:20 UTC
The problem only happens if the randomly generated NSS database password contains a backslash character. As a workaround, specify a fixed password without backslash, for example: [DEFAULT] pki_pin=Secret.123 Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request. *** Bug 1459337 has been marked as a duplicate of this bug. *** [root@cloud-qe-19 ~]# rpm -qi pki-ca Name : pki-ca Version : 10.4.1 Release : 9.el7 Architecture: noarch Install Date: Wed 14 Jun 2017 09:37:00 AM EDT Group : System Environment/Daemons Size : 2308437 License : GPLv2 Signature : (none) Source RPM : pki-core-10.4.1-9.el7.src.rpm Build Date : Tue 13 Jun 2017 02:08:27 PM EDT Build Host : ppc-046.build.eng.bos.redhat.com Relocations : (not relocatable) Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> Vendor : Red Hat, Inc. URL : http://pki.fedoraproject.org/ Summary : Certificate System - Certificate Authority pkispawn was successful after trying a couple of times. Do we want to fail pkispawn with an appropriate error message if a pin with \ is provided in the installation file? Yes, we can add some code to check user-provided password validity and generate the proper error message. Feel free to change the ticket to ASSIGNED or open a new ticket. Opened a new bug for comment 14 https://bugzilla.redhat.com/show_bug.cgi?id=1462973 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 |