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://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/installing_satellite_server_in_a_connected_network_environment/index?lb_target=preview

https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/installing_satellite_server_in_a_disconnected_network_environment/index?lb_target=preview&check_logged_in=1



Section Number and Name: 


1.6. Ports and Firewalls Requirements

Table 1.3. Satellite Server incoming traffic


Describe the issue: 


We describe the usage of port 8443 in that specific table as well but port 8443 is not used by any services on the Satellite server itself to have a need of establishing an incoming connection. 

Suggestions for improvement: 

Consult with product engineers and then further remove port 8443's description from "Table 1.3. Satellite Server incoming traffic" only ( for both connected and disconnected satellite installations ) 

Additional information: 

Perhaps the same change is needed for Sat 6.12 as well.

That's correct. 8443 is not used on the Satellite at all (anymore).

It *is* used on the Capsule, but even there the use is deprecated since 6.11 as the same requests can be made on port 443 too.

Okay. So, shall we completely remove the row of Port 8443 from Connected, Disconnected, and Capsule?
This will be applicable to versions 6.13, 6.12, and 6.11.

@egolov

I think it should be merged with the other entry for "Content Host Registration" on port 443, as the features are used over that port

Link to the PR: https://github.com/theforeman/foreman-documentation/pull/2008

*** Bug 2175364 has been marked as a duplicate of this bug. ***

Link to the updated documents: https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/installing_satellite_server_in_a_connected_network_environment/index?lb_target=preview&check_logged_in=1#Ports_and_Firewalls_Requirements_satellite

Link to the updated and published documents: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/installing_satellite_server_in_a_connected_network_environment/preparing_your_environment_for_installation_satellite#Ports_and_Firewalls_Requirements_satellite