Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJoniel Pasqualetto
2022-08-10 20:20:05 UTC
Description of problem:
Having an upstream Satellite using custom certs, which require a CA bundle, when configuring a downstream Satellite, only the first certificate of the bundle is used.
Therefore, if the first certificate of the bundle is not the Root CA, but an intermediate, the validation against the certificate chain provided by the upstream Satellite fails.
Version-Release number of selected component (if applicable):
Satellite 6.11
How reproducible: always, depending on how the user built their CA bundle.
Steps to Reproduce:
1. Create a Satellite server to be used as upstream. Configure it with custom certificates signed by an intermediate CA.
RootCA -> Intermediate -> Satellite Certificate
2. Create a Satellite server to be used as downstream. Create a content certificate containing the bundle certificate used to sign the upstream certificates. The bundle must be create using first the intermediate CA then the root ca.
3. On the downstream satellite, go to Content -> Subscriptions -> manage manifest -> Cdn Configuration -> Network Sync. Point it to the upstream SAtellite and choose the content credential create on step 2.
Actual results:
Fail with an SSL Error: SSL_connect returned=1 errno=0 state=error: certificate verify failed (self signed certificate in certificate chain) (OpenSSL::SSL::SSLError)
Expected results:
Should work, considering that the complete CA bundle was added to the content credential.
Additional info:
Possible workarounds:
- Change the order of the certificates inside the content credential, putting the Root CA first
- Create the content credential ONLY WITH THE ROOT CA.
Multiple certificates can be entered in content-credential. Synchronization using Network Sync and Custom CDN works no matter on certificates order.
VERIFIED with Satellite 6.12 SNAP13 @RHEL8.6
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 (Important: Satellite 6.12 Release), 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-2022:8506