I would like to see the Capsule change the incoming port 80 request from the to port 443 between the Capsule and the Satellite Server. It is essential that all communications between the Satellite Server and the Capsule be encrypted.

@david what communication case are we talking about? I'm not aware about a case where communication between satellite and capsule would not go over ssl. The port on satellite side used is 443 and on capsule side 9090 (but it's still SSL)

To the subject of the BZ request itself. I assume (and correct me if I'm wrong) the request is not about turning on SSL, but rather making the 80 port configurable on all the places that it's hardcoded right now (there are reasons we don't use SSL, such as Anaconda constraints on https).

I see this places, where the 80 port is hardcoded:

1. unattended templates when getting from satellite server
  - a workaround for this is using a templates capsule module (turned on by default on every capsule), by default serving the templates on port 8000 and it should be configurable by `--foreman-proxy-template-url` option

2. the non-https yum repositories served by satellite

3. the location of bootstrap rpms (https://satellite.example.com/pub/)

It seems to me (correct me, if I'm wrong) that the 2. is the main request of the BZ, right?

@Ivan
Customer's security team blocks any traffic on port 80 between

a) satellite->capsule
b) satellite->client
c) capsule->client
d) redhat cdn->satellite

If port 80 is mandatory in satellite/capsule (such as for provisioning, kickstart, repo sync, remote execution, monitoring etc) then we need this port to be configurable to other port. 

In other words, we need to figure-out what all tasks is compulsorily using port 80 in satellite/capsule server. Specially if it involves traffic as above in a,b,c,d. Can we use any other port for same tasks? and how can we configure that in sat/capsule?

From the above comment, I can find there are 3 scenarios which uses port 80.
1 has a solution
2 how can we use any other port for same piece of work.
3 same as 2

Thanks.

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.