From 802a54bfc8b698ca962b383beb3684a4b1af1865 Mon Sep 17 00:00:00 2001 From: Alexander Bokovoy Date: Mon, 5 Aug 2019 17:22:44 +0300 Subject: [PATCH] Change RA agent certificate profile to caSubsystemCert Currently, RA agent certificate is issued using caServerCert profile. This has unfortunate side effect of asserting id-pk-serverAuth EKU which is not really needed for RA agent. If IPA CA certificate adds SAN DNS constraints into issued certificates, presence of id-pk-serverAuth EKU forces NSS (and other crypto libraries) to validate CN value with regards to SAN DNS constraints, due to historical use of CN bearing DNS name. Since RA agent certificate has 'CN=IPA RA', it is guaranteed to fail the check. Default IPA CA configuration does *not* add SAN DNS constraints into RA agent certificate. However, it is better to be prepared to such behavior. Related: https://bugzilla.redhat.com/1670239 Reviewed-By: Fraser Tweedale Reviewed-By: Christian Heimes --- ipalib/constants.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ipalib/constants.py b/ipalib/constants.py index 3bc042ede..ad5261ff0 100644 --- a/ipalib/constants.py +++ b/ipalib/constants.py @@ -306,7 +306,7 @@ IPA_CA_RECORD = "ipa-ca" IPA_CA_NICKNAME = 'caSigningCert cert-pki-ca' RENEWAL_CA_NAME = 'dogtag-ipa-ca-renew-agent' RENEWAL_REUSE_CA_NAME = 'dogtag-ipa-ca-renew-agent-reuse' -RA_AGENT_PROFILE = 'caServerCert' +RA_AGENT_PROFILE = 'caSubsystemCert' # How long dbus clients should wait for CA certificate RPCs [seconds] CA_DBUS_TIMEOUT = 120