Bug 1562423
Summary: | SAN in internal SSL server certificate in pkispawn configuration step | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Marc Sauton <msauton> | |
Component: | pki-core | Assignee: | Christina Fu <cfu> | |
Status: | CLOSED ERRATA | QA Contact: | Asha Akkiangady <aakkiang> | |
Severity: | high | Docs Contact: | Marc Muehlfeld <mmuehlfe> | |
Priority: | high | |||
Version: | 7.6 | CC: | cfu, mharmsen, ssidhaye | |
Target Milestone: | rc | Keywords: | TestCaseProvided, ZStream | |
Target Release: | 7.6 | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Enhancement | ||
Doc Text: |
Certificate System now adds the SAN extension to server certificates
With this update, Certificate System adds the Subject Alternative Name (SAN) extension by default to server certificates and sets it to the Common Name (CN) of the certificate.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1581135 (view as bug list) | Environment: | ||
Last Closed: | 2018-10-30 11:05:27 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1581135 |
Description
Marc Sauton
2018-03-30 16:40:03 UTC
Per RHEL 7.5.z/7.6/8.0 Triage: 7.5.z cfu: I think this one is very much worthwhile to be done in 7.5 Test Procedure: * Install a CA (with single step pkispawn is good): When complete, check that its SSL server cert bears the Subject Alternative Name (SAN) extension that matches the CN of the cert. * Install a KRA (on a separate Tomcat instance; (with single step pkispawn is good)): When complete, check that its SSL SSL server cert bears the Subject Alternative Name (SAN) extension that matches the CN of the cert. * You could test install another subsystem (e.g. subCA) and do the same check. It should be enough, as far as installation goes. * Since I changed all *Server* profiles (not limited to the *InternalAuthServerCert* ones), you can manually test those too. * Note that it appears that I have added the changes to the caCMC*server* ones previously. You could go through CMC enrollment procedure and check them as well. commit 7eae0d840c1b7494db2cea67744366fe409eafea (HEAD -> DOGTAG_10_5_BRANCH, origin/DOGTAG_10_5_BRANCH, ticket-2995-defaultSANinServerProfiles-r2) Author: Christina Fu <cfu> Date: Thu May 17 19:36:10 2018 -0700 Ticket #2995 SAN in internal SSL server certificate in pkispawn configuration step This patch adds CommonNameToSANDefault to all server profiles so that SAN will be placed in server certs by default. For more flexible SAN or multi-value SAN, SubjectAltNameExtDefault will have to be used instead. fixes: https://pagure.io/dogtagpki/issue/2995 Change-Id: I66556f2cb8ed4e1cbe2d0949c5848c6978ea9641 Build used for verification: root@csqa4-guest01 BZ1471935 # rpm -qi pki-base Name : pki-base Version : 10.5.9 Release : 5.el7 Architecture: noarch Install Date: Sun 12 Aug 2018 04:20:59 AM EDT Group : System Environment/Base Size : 2122224 License : GPLv2 Signature : RSA/SHA256, Thu 09 Aug 2018 08:38:50 PM EDT, Key ID 199e2f91fd431d51 Source RPM : pki-core-10.5.9-5.el7.src.rpm Build Date : Thu 09 Aug 2018 08:25:40 PM EDT Build Host : ppc-021.build.eng.bos.redhat.com Relocations : (not relocatable) Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> Vendor : Red Hat, Inc. URL : http://pki.fedoraproject.org/ Summary : Certificate System - PKI Framework CA certificate: Subject: CN=csqa4-guest01.idm.lab.eng.rdu.redhat.com,OU=rhcs94-CA-ssidhaye,O=Example-rhcs94-CA Identifier: Subject Alternative Name - 2.5.29.17 Critical: no Value: DNSName: csqa4-guest01.idm.lab.eng.rdu.redhat.com ================================= KRA Certificate: Subject: CN=csqa4-guest01.idm.lab.eng.rdu.redhat.com,OU=rhcs94-KRA-ssidhaye,O=Example-rhcs94-CA Identifier: Subject Alternative Name - 2.5.29.17 Critical: no Value: DNSName: csqa4-guest01.idm.lab.eng.rdu.redhat.com ========================================= Certificate information using CMC enrollment: Subject: CN=csqa4-guest01.idm.lab.eng.rdu.redhat.com,OU=pki-tomcat,O=mySecurityDomain Identifier: Subject Alternative Name - 2.5.29.17 Critical: no Value: DNSName: csqa4-guest01.idm.lab.eng.rdu.redhat.com ================================================= Sub CA Certificate: Subject: CN=csqa4-guest01.idm.lab.eng.rdu.redhat.com,OU=rhcs94-SubCA-ssidhaye,O=Example-rhcs94-SubCA Identifier: Subject Alternative Name - 2.5.29.17 Critical: no Value: DNSName: csqa4-guest01.idm.lab.eng.rdu.redhat.com 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://access.redhat.com/errata/RHBA-2018:3195 |