Bug 1391206 - Candlepin consumer certificate subject alternative name uses URI incorrectly
Summary: Candlepin consumer certificate subject alternative name uses URI incorrectly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Candlepin
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: 6.4.0
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On: 1395747
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-02 19:07 UTC by Stephen Benjamin
Modified: 2019-11-05 23:02 UTC (History)
4 users (show)

Fixed In Version: candlepin-2.1.1-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1395747 (view as bug list)
Environment:
Last Closed: 2018-10-16 18:59:22 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Stephen Benjamin 2016-11-02 19:07:54 UTC
Description of problem:
The consumer certificate generated for a client in /etc/pki/consumer has a CN w/ the UUID, and a SAN containing the host name, but it is marked as a URI instead of DNS name.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Register a client to Satellite
2. Examine the consumer certificate w/ openssl x509 -text -noout -in /etc/pki/consumer/cert.pem


Actual results:

Certificate contains a Subject Alternative Name of a URI type
            X509v3 Subject Alternative Name: 
                URI:CN=sat-rhel7.example.com



Expected results:
SAN is a DNS Name.

Additional info:
Standard says if using URI it should actually be a URI.

Comment 7 Lukáš Hellebrandt 2018-09-24 13:51:21 UTC
Verified with Sat 6.4 snap 22.

The host name is not called URI anymore:

# openssl x509 -text -noout -in /etc/pki/consumer/cert.pem | grep 'Subject Alternative' -A1
            X509v3 Subject Alternative Name: 
                DirName:/CN=f319450d-a8b7-4ebd-9fbb-9261cd342531, DirName:/CN=<FQDN>

Comment 8 Bryan Kearney 2018-10-16 18:59:22 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://access.redhat.com/errata/RHSA-2018:2927


Note You need to log in before you can comment on or make changes to this bug.