| Summary: | CA fails to start after doing ipa-ca-install --external-ca | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jaroslav Reznik <jreznik> | ||||
| Component: | ipa | Assignee: | IPA Maintainers <ipa-maint> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Kaleem <ksiddiqu> | ||||
| Severity: | unspecified | Docs Contact: | Marc Muehlfeld <mmuehlfe> | ||||
| Priority: | high | ||||||
| Version: | 7.3 | CC: | akasurde, edewata, ipa-maint, jcholast, mbasti, mmuehlfe, nsoman, pvoborni, rcritten, tkrizek, tscherf | ||||
| Target Milestone: | rc | Keywords: | ZStream | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| 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.
|
Story Points: | --- | ||||
| Clone Of: | 1318616 | Environment: | |||||
| Last Closed: | 2016-12-06 17:02:33 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Bug Depends On: | 1318616 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Jaroslav Reznik
2016-10-27 09:35:07 UTC
Created attachment 1219175 [details]
console.log
Verified using IPA version :: ipa-4.4.0-14.el7_3 Marking BZ as verfied. 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 |