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.
Document URL:
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/API_Guide/chap-Red_Hat_Satellite-API_Guide-Introduction_to_Red_Hat_Satellite.html
Section Number and Name:
wherever fits best
Describe the issue:
The docs currently only talk about talking HTTPS to the Satellite machine if one needs the API and do not mention how the API can be accessed via the Capsule. The naïve user would try to talk HTTPS (on port 443) to the Capsule too and fail as the proxy is on port 8443.
Suggestions for improvement:
Document the API ports for Satellite as being 443 and Capsule as being 8443.
Additional information:
Another solution could be to proxy the API on 443, not sure what's best here.
JFTR for everyone implementing this (and this probably should also go to the docs). You can read the correct port needed from /etc/rhsm/rhsm.conf* in "port" of the "server" section. Thus this can be fully automated and does not need any guessing about "who to speak to".
*obviously, only if the machine is subscribed to Satellite/Capsule
commit 0fffd9c8800e4e1af9ce06e838844498553e369d
Author: David O'Brien <daobrien>
Date: Tue Feb 16 12:49:07 2016 +1000
bz1297724 Expand example and description on API access.
Included #c5 in BZ about modifying URL to include port number.
Included #c6 about determining port numbers from rhsm.conf file.