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.
Bug 2251075 - foreman-proxy/9090 it's not presenting the complete chain when using custom certs
Summary: foreman-proxy/9090 it's not presenting the complete chain when using custom c...
Keywords:
Status: CLOSED DUPLICATE of bug 2239494
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Proxy
Version: 6.14.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-11-22 18:27 UTC by Waldirio M Pinheiro
Modified: 2023-11-22 18:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-22 18:36:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-21466 0 None None None 2023-11-22 18:28:05 UTC

Description Waldirio M Pinheiro 2023-11-22 18:27:26 UTC 
Description of problem:
When using custom certs, we cannot see the complete chain when hitting the port 9090

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

How reproducible:
100%

Steps to Reproduce:
1. Install satellite
2. Deploy custom-certs
3. Hit the port 443 and 9090

Actual results:
The 9090 will present a single chain pointing to the intermediate

Expected results:
See the complete chain

Additional info:
Comment 1 Waldirio M Pinheiro 2023-11-22 18:36:21 UTC 
Hello,

When using the self-sign certs, we can see the full chain, as presented below

443
=====
$ echo | openssl s_client -connect wallsat614.d.sysmgmt.cee.redhat.com:443
...
Certificate chain
 0 s:C = US, ST = North Carolina, O = Katello, OU = SomeOrgUnit, CN = wallsat614.d.sysmgmt.cee.redhat.com
   i:C = US, ST = North Carolina, L = Raleigh, O = Katello, OU = SomeOrgUnit, CN = wallsat614.d.sysmgmt.cee.redhat.com
   a:PKEY: rsaEncryption, 4096 (bit); sigalg: RSA-SHA256
   v:NotBefore: Nov 11 00:45:18 2023 GMT; NotAfter: Jan 18 00:45:20 2038 GMT
 1 s:C = US, ST = North Carolina, L = Raleigh, O = Katello, OU = SomeOrgUnit, CN = wallsat614.d.sysmgmt.cee.redhat.com
   i:C = US, ST = North Carolina, L = Raleigh, O = Katello, OU = SomeOrgUnit, CN = wallsat614.d.sysmgmt.cee.redhat.com
   a:PKEY: rsaEncryption, 4096 (bit); sigalg: RSA-SHA256
   v:NotBefore: Nov 18 00:45:12 2023 GMT; NotAfter: Jan 18 00:45:12 2038 GMT
...
=====


9090
=====
$ echo | openssl s_client -connect wallsat614.d.sysmgmt.cee.redhat.com:9090
...
Certificate chain
 0 s:C = US, ST = North Carolina, O = FOREMAN, OU = SMART_PROXY, CN = wallsat614.d.sysmgmt.cee.redhat.com
   i:C = US, ST = North Carolina, L = Raleigh, O = Katello, OU = SomeOrgUnit, CN = wallsat614.d.sysmgmt.cee.redhat.com
   a:PKEY: rsaEncryption, 4096 (bit); sigalg: RSA-SHA256
   v:NotBefore: Nov 11 00:45:30 2023 GMT; NotAfter: Jan 18 00:45:32 2038 GMT
 1 s:C = US, ST = North Carolina, L = Raleigh, O = Katello, OU = SomeOrgUnit, CN = wallsat614.d.sysmgmt.cee.redhat.com
   i:C = US, ST = North Carolina, L = Raleigh, O = Katello, OU = SomeOrgUnit, CN = wallsat614.d.sysmgmt.cee.redhat.com
   a:PKEY: rsaEncryption, 4096 (bit); sigalg: RSA-SHA256
   v:NotBefore: Nov 18 00:45:12 2023 GMT; NotAfter: Jan 18 00:45:12 2038 GMT
...
=====

However, when using the custom certs, this is the output

# echo | openssl s_client -connect $(hostname):443
---
Certificate chain
 0 s:CN = wallsat614customcert.d.sysmgmt.cee.redhat.com
   i:C = CA, ST = British Columbia, O = Wallys Co, OU = Wallys Co CA-IT, CN = Wallys Intermediate CA
 1 s:C = CA, ST = British Columbia, O = Wallys Co, OU = Wallys Co CA-IT, CN = Wallys Intermediate CA
   i:C = CA, ST = British Columbia, L = New Westminster, O = Wallys Co, OU = Wallys Co CA-IT, CN = Wallys Root CA, emailAddress = waldirio
 2 s:C = CA, ST = British Columbia, L = New Westminster, O = Wallys Co, OU = Wallys Co CA-IT, CN = Wallys Root CA, emailAddress = waldirio
   i:C = CA, ST = British Columbia, L = New Westminster, O = Wallys Co, OU = Wallys Co CA-IT, CN = Wallys Root CA, emailAddress = waldirio
---


# echo | openssl s_client -connect $(hostname):9090
---
Certificate chain
 0 s:CN = wallsat614customcert.d.sysmgmt.cee.redhat.com
   i:C = CA, ST = British Columbia, O = Wallys Co, OU = Wallys Co CA-IT, CN = Wallys Intermediate CA
---


One important information, though. When redirecting the complete output, we can see the depth info, which presents the complete chain
---
# echo | openssl s_client -connect $(hostname):443 &>/tmp/443.log

[root@wallsat614customcert ~]# head -n 20 /tmp/443.log 
depth=2 C = CA, ST = British Columbia, L = New Westminster, O = Wallys Co, OU = Wallys Co CA-IT, CN = Wallys Root CA, emailAddress = waldirio
verify return:1
depth=1 C = CA, ST = British Columbia, O = Wallys Co, OU = Wallys Co CA-IT, CN = Wallys Intermediate CA
verify return:1
depth=0 CN = wallsat614customcert.d.sysmgmt.cee.redhat.com
verify return:1
CONNECTED(00000003)
---
Certificate chain
 0 s:CN = wallsat614customcert.d.sysmgmt.cee.redhat.com
   i:C = CA, ST = British Columbia, O = Wallys Co, OU = Wallys Co CA-IT, CN = Wallys Intermediate CA
 1 s:C = CA, ST = British Columbia, O = Wallys Co, OU = Wallys Co CA-IT, CN = Wallys Intermediate CA
   i:C = CA, ST = British Columbia, L = New Westminster, O = Wallys Co, OU = Wallys Co CA-IT, CN = Wallys Root CA, emailAddress = waldirio
 2 s:C = CA, ST = British Columbia, L = New Westminster, O = Wallys Co, OU = Wallys Co CA-IT, CN = Wallys Root CA, emailAddress = waldirio
   i:C = CA, ST = British Columbia, L = New Westminster, O = Wallys Co, OU = Wallys Co CA-IT, CN = Wallys Root CA, emailAddress = waldirio
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIGIDCCBAigAwIBAgICEAMwDQYJKoZIhvcNAQELBQAwdzELMAkGA1UEBhMCQ0Ex
GTAXBgNVBAgMEEJyaXRpc2ggQ29sdW1iaWExEjAQBgNVBAoMCVdhbGx5cyBDbzEY
---

*** This bug has been marked as a duplicate of bug 2239494 ***
Note You need to log in before you can comment on or make changes to this bug.