Bug 1367759

Summary: [RFE] [webui] warn admin if there is only one IPA server with CA
Product: Red Hat Enterprise Linux 7 Reporter: Martin Bašti <mbasti>
Component: ipaAssignee: Varun Mylaraiah <mvarun>
Status: CLOSED ERRATA QA Contact: Kaleem <ksiddiqu>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.3CC: mvarun, nsoman, pvoborni, rcritten
Target Milestone: rcKeywords: FutureFeature
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 06:01:20 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
Verified on ipa-server-4.4.0-10.el7.x86_64 none

Description Martin Bašti 2016-08-17 12:02:53 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/5828

Having only one IPA server with CA is very dangerous because CA cannot be installed if CA certificate private keys are lost. In such case it is required to recreate all certs which is a very tedious process.

With introduction of [http://www.freeipa.org/page/V4/Server_Roles server roles] web ui will receive information of how many CA exist in a topology.

Web UI should warn admins at a server role page if there is only one replica with CA.
Comment 1 Martin Bašti 2016-08-17 12:04:06 UTC 
Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/d45b0efe5d5f718791d34a3e57ea723dcae8fd59
https://fedorahosted.org/freeipa/changeset/ff51e43a3eb2431f253a25351b1b6378224c4b66
Comment 3 Varun Mylaraiah 2016-09-16 13:43:38 UTC 
Created attachment 1201645 [details]
Verified on ipa-server-4.4.0-10.el7.x86_64
Comment 5 errata-xmlrpc 2016-11-04 06:01:20 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