-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
6.12.0
-
False
-
-
False
-
CLOSED
-
1,400
Description of problem:
In few environments, security is unlikely to allow traffic on port 80 between satellite server and capsule/client in secure networks.
Any way this connection can be changed from port 80 (uncoded) to another port which is encrypted?
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
- Provisioning failed to fetch the Vmlinuz and getting timeout.
- Customer's security team blocks any traffic on port 80 between
a) satellite->capsule
b) satellite->client
c) capsule->client
If port 80 is mandatory in satellite/capsule (such as registration/provisioning) then we need this port to be configurable to other encrypted port.
Expected results:
- Provisioning shall work using encrypted port other than port 80.
- Customer should configure ports (other than port 80) in satellite server to communicate between satellite and capsule/clients. Currently, port 80 is hard coded in satellite server.
Additional info:
- is duplicated by
-
SAT-21084 [RFE] Global Registration Method should not use port 80 for any purposes
- Closed
-
SAT-17754 How to configure another port (other than port 80) in satellite server for communicating between the Satellite server and client?
- Closed
- relates to
-
SAT-28583 Registration of hosts via capsule should not need to use port 9090 additionally
- Backlog
- external trackers
- links to