Hide Forgot
This bug has been copied from bug #1301687 and has been proposed to be backported to 7.2 z-stream (EUS).
Upstream ticket: https://fedorahosted.org/freeipa/ticket/4492
Jan, please provide impact of missing fix for Bug 1301546 and what are the possible workarounds
The impact is that installing a replica with a CA is not possible against a master which uses a 3rd party cert for httpd. The workaround is to issue a (temporary) IPA cert for httpd on the master before installing the replica: # certutil -d /etc/httpd/alias -L -n $NICKNAME -r >backup.crt.der # ipa service-mod HTTP/$HOSTNAME --certificate= # ipa-getcert start-tracking -d /etc/httpd/alias -n $NICKNAME -p /etc/httpd/alias/pwdfile.txt -C /usr/lib64/ipa/certmonger/restart_httpd # ipa-getcert resubmit -d /etc/httpd/alias -n $NICKNAME -K HTTP/$HOSTNAME After installing the replica, you can revert to the original cert: # ipa-getcert stop-tracking -d /etc/httpd/alias -n $NICKNAME # certutil -d /etc/httpd/alias -D -n $NICKNAME # certutil -d /etc/httpd/alias -A -n $NICKNAME -t ,, -i backup.crt.der # systemctl restart httpd
Verified using IPA server version :: ipa-server-4.2.0-15.el7_2.10.x86_64 Please find the console.log for each ticket in attachments. For https://fedorahosted.org/freeipa/ticket/5636 ticket, there is another bug reported - BZ1318616
Created attachment 1137376 [details] tkt_4492.log
Created attachment 1137377 [details] tkt_5595.log
Created attachment 1137379 [details] tkt_5598.log
Created attachment 1137381 [details] tkt_5611.log
The workaround for bug 1318616 is to run ipa-certupdate right after ipa-ca-install. To make the workaround actually work, the fix for IPA ticket 5506 needs to be included as well. Moving back to POST.
Upstream ticket: https://fedorahosted.org/freeipa/ticket/5506
Verified using IPA version with workaround suggested in comment#14 ipa-server-4.2.0-15.el7_2.12.x86_64 See attachment for console.log.
Created attachment 1137687 [details] tkt_5636.log
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-1036.html