Description of problem:

In particular environment, security is unlikely to allow traffic on port 80 between satellite server and clients in secure networks.

a) Is there a workaround for configuring port 80 in satellite server?
b) How to configure another port (other than port 80) in satellite server for communicating between the Satellite server and clients?

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

• The use of port 80 is a one-time thing for provisioning only, at least for everything. The kickstart template, installation media, and downloading the subscription-manager configuration RPM all use port 80.
• The configuration RPM is hard coded to use port 80, and the installation media is too hard coded. The Template could be moved to a different port like 8000 using the templates proxy, but that doesn't get you anything if the other 2 uses are going through 80.

Expected results:
Customer should configure ports (other than port 80) in satellite server to communicate between satellite and clients. Currently, port 80 is hard coded in satellite server.

Additional info: