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.
DescriptionKeith Robertson
2016-02-11 21:47:48 UTC
Cloning this bug for 6.2.0
+++ This bug was initially created as a clone of Bug #1306847 +++
The REST endpoints on redhat.com that enable the Satellite 6 Red Hat Access plug-in will sunset CORS support soon. To ensure that the Red Hat Access plug-in, continues to function in Satellite 6 all client calls must be proxied through the Satellite 6 server to REST endpoints on redhat.com.
This BZ enables this capability. It is important to note that the proxy will *only* proxy traffic to the approved REST endpoints on RH.com and nowhere else and this proxy is only to enable the services provided the plug-in[1]
[1] https://access.redhat.com/articles/899803
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/RHBA-2016:1501