Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-14987

Host provisioning should rely only on port 443

XMLWordPrintable

      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:

              ehelms@redhat.com Eric Helms
              rhn-support-pbadguja Pranjal Badgujar
              RH Bugzilla Integration RH Bugzilla Integration
              Votes:
              4 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated: