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.
DescriptionMark Meierjohann
2015-12-09 07:27:43 UTC
Description of problem:
Too many ports required for communication between Capsule and Satellite as well as Satellite and Capsule.
Too many ports required for communication between Client and Capsule.
Version-Release number of selected component (if applicable): 6.1
As described in the documentation
( https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/sect-Red_Hat_Satellite-Installation_Guide-Red_Hat_Satellite_Capsule_Server_Prerequisites.html#sect-Red_Hat_Satellite-Installation_Guide-Red_Hat_Satellite_Capsule_Server_Prerequisites-Network_Ports_Required_for_Capsule_Communications )
we require ports 443, 5646 and 5647 ( all TCP ) between the Capsule and the Satellite, as well as 9090/TCP between the Satellite and the Capsule. These requirements make managing public-cloud workloads with a satellite/capsule architecture impossible for some enterprises, due to the amount of firewall rules required.
In addition the number of ports required Client management between the client and the capsule are causing an issue if there is a firewall between the Client and the Capsule: 443 5647 8140 8443 9090 all TCP.
A number of security conscience customers, financial and government, can not get Satellite into operations with these requirements. Communication initiated both ways between Satellite and Capsule is a show-stopper.
Ideally these customers would like to see one port (443/TCP) that can be proxied through a web-application firewall or a web-proxy based http CONNECT for both client to capsule and capsule to Satellite communication.
I do not believe we will do this in any reasonable amount of time. While I understand the value this would bring, the work would be large, and I do not expect us to do it any time soon.