Bug 1360769

Summary: ipa-server-certinstall couldnt unlock private key file
Product: Red Hat Enterprise Linux 7 Reporter: Martin Bašti <mbasti>
Component: ipaAssignee: IPA Maintainers <ipa-maint>
Status: CLOSED ERRATA QA Contact: Kaleem <ksiddiqu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: jcholast, jhrozek, pvoborni, rcritten
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-4.4.0-8.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 05:59:15 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:
Attachments:
Description Flags
console output with verification steps none

Description Martin Bašti 2016-07-27 12:41:36 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/6032

ipa-server-certinstall -w file.pem file.key asks for an unlock passwort for private key. This is happen if the private key file is encrypted and if it isnt encrypted. If i type in the correct passwort the result ist:

Insufficient access:  Invalid credentials
Comment 1 Jan Cholasta 2016-08-17 13:09:00 UTC 
Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/4ee426a68ec60370eee6f5aec917ecce444840c7
Comment 3 Kaleem 2016-09-15 08:48:13 UTC 
Verified.

IPA Version:
============
root@dhcp207-129 ~]# rpm -q ipa-server
ipa-server-4.4.0-11.el7.x86_64
[root@dhcp207-129 ~]# 

Please find the attached file for console output of verification steps.
Comment 4 Kaleem 2016-09-15 08:49:03 UTC 
Created attachment 1201160 [details]
console output with verification steps
Comment 6 errata-xmlrpc 2016-11-04 05:59:15 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://rhn.redhat.com/errata/RHBA-2016-2404.html