summaryrefslogtreecommitdiffstats
path: root/po
diff options
context:
space:
mode:
authorFraser Tweedale <ftweedal@redhat.com>2016-10-20 14:42:17 +1000
committerJan Cholasta <jcholast@redhat.com>2016-11-11 07:05:14 +0100
commitcdd41e06e6ef97efafd36ee9e4c8d3be9e4099e7 (patch)
tree241b9f5b8c765525652a21d275643ecfa3d2e8ff /po
parent2644c955489ee5b22ecc0227c5cd8ed1e90ee648 (diff)
downloadfreeipa-cdd41e06e6ef97efafd36ee9e4c8d3be9e4099e7.tar.gz
freeipa-cdd41e06e6ef97efafd36ee9e4c8d3be9e4099e7.tar.xz
freeipa-cdd41e06e6ef97efafd36ee9e4c8d3be9e4099e7.zip
Ensure correct IPA CA nickname in DS and HTTP NSSDBs
During replica installation, if the IPA deployment has a custom subject_base, the routines that create the DS and HTTP NSSDBs erroneously compare the subject of CA certs to the *default* subject base. This causes the IPA CA cert to be added to the NSSDBs with a nickname derived from the subject name, instead of "{REALM} IPA CA". At a later stage of installation, the `upload_cacrt` plugin reads certs from the HTTP NSSDB in order to update the cn=certificates LDAP certstore. The NSSDB nickname of the cert is used as the CN for the entry. Because the IPA CA cert was not installed in the HTTP NSSDB with the "{REALM} IPA CA", this causes a spurious entry for the IPA CA to be added to the certstore. To avoid this scenario, use the deployment's actual subject base when deciding if a cert is the IPA CA cert. Fixes: https://fedorahosted.org/freeipa/ticket/6415 Reviewed-By: Tomas Krizek <tkrizek@redhat.com>
Diffstat (limited to 'po')
0 files changed, 0 insertions, 0 deletions