Bug 1389249 - CA fails to start after doing ipa-ca-install --external-ca
Summary: CA fails to start after doing ipa-ca-install --external-ca
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Kaleem
Marc Muehlfeld
URL:
Whiteboard:
Depends On: 1318616
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-27 09:35 UTC by Jaroslav Reznik
Modified: 2016-12-06 17:02 UTC (History)
11 users (show)

Fixed In Version: ipa-4.4.0-13.el7_3
Doc Type: If docs needed, set a value
Doc Text:
When using a previously-installed third-party certificate to sign the certificate signing request (CSR) during an Identity Management (IdM) external certificate authority (CA) installation, the third-party certificate trust flags in the network security services (NSS) database were reset. Consequently, the certificate was no longer marked as trusted, and the IdM CA installation failed. This update applies a patch and as a result, installing an IdM CA works correctly in the described scenario.
Clone Of: 1318616
Environment:
Last Closed: 2016-12-06 17:02:33 UTC
Target Upstream Version:

Attachments (Terms of Use)
console.log (14.04 KB, text/plain)
2016-11-10 05:49 UTC, Abhijeet Kasurde 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2863 0 normal SHIPPED_LIVE ipa bug fix update 2016-12-06 22:00:06 UTC

Description Jaroslav Reznik 2016-10-27 09:35:07 UTC 
This bug has been copied from bug #1318616 and has been proposed
to be backported to 7.3 z-stream (EUS).
Comment 5 Abhijeet Kasurde 2016-11-10 05:49:03 UTC 
Created attachment 1219175 [details]
console.log
Comment 6 Abhijeet Kasurde 2016-11-10 05:50:39 UTC 
Verified using IPA version ::
ipa-4.4.0-14.el7_3

Marking BZ as verfied.
Comment 10 errata-xmlrpc 2016-12-06 17:02:33 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-2863.html
Note You need to log in before you can comment on or make changes to this bug.