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 1743839 - [RFE] Officially support core Satellite API proxy via Capsule port 8443
Summary: [RFE] Officially support core Satellite API proxy via Capsule port 8443
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
: 2278906 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-20 19:11 UTC by Mike McCune
Modified: 2024-05-06 12:26 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Mike McCune 2019-08-20 19:11:38 UTC 
With isolated clients who only have access to the Capsule in a Satellite customer environments they are currently relying on access to the core Satellite API via the proxy route provided by the Capsule to our API at:

https://capsule.example.com:8443/api/<ENDPOINT>

This works currently without issue but this is not something we officially support.

This RFE is to codify official support via documentation and some simple tests that ensure basic API accessibility via the Capsule -> Satellite.

This is used in environments where automation needs to access the Satellite API from the network where the Capsule is the proxy to get to the Satellite.
Comment 4 Gary Scarborough 2019-10-14 13:28:27 UTC 
Business justification for my customer:

Hello Gary,

Yes, anything you can find out would be greatly appreciated.  We're working against a clock here (big-time) and I don't believe the team will receive sign-off until it can be officially stated that calling the API via the capsule URL:8443 is supported in the current architecture (6.5.2.1 at present).

There seems to be conflicting information between what the documentation states - e.g. https://access.redhat.com/documentation/en-us/red_hat_satellite/6.5/html/api_guide/chap-red_hat_satellite-api_guide-using_the_red_hat_satellite_api#sect-Working_with_Hosts - and what Red Hat engineering has indicated.  Management is looking for an engineering sign-off as you might expect, because it will have serious ramifications if the satellite API call via capsule suddenly stops working due to an upgrade to satellite/capsules, as well if simply breaks under the current revision because it's not officially not supported.
Comment 5 Mike McCune 2019-10-14 15:26:51 UTC 
** Usage of port 8443 for accessing the Satellite API is officially supported by Red Hat Engineering and will not be removed from the product without proper deprecation notice and release cycle as well as a suitable replacement method for calling the Satellite API from clients behind a Capsule. The likely change in the future would be to shift to using port 443 but this is not planned and unlikely to happen within any of the upcoming planned releases of Satellite 6. 

On a more technical note, we have components that Satellite itself relies on accessing the API via 8443, so we are relying on this API route for proper functionality of Satellite and associated tools.
Comment 7 Ewoud Kohl van Wijngaarden 2021-09-16 14:35:17 UTC 
I still argue that exposing the Foreman (+ plugins) is something Satellite should actually stop doing. You are isolating clients and the Foreman API is a potential attack vector. With global registration it we can phase out bootstrap.py and properly do registration using dedicated APIs. That means only the RHSM API is needed, not the full Foreman API.
Comment 8 Eric Helms 2024-05-06 12:26:28 UTC 
*** Bug 2278906 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.