Description of problem:
While Satellite listens for RHSM requests (of clients machine registered to it) on port 443, an external Capsule (offering just a subset of Satellite functionality) has separate port 8443 dedicated for it.

This is confusing and can easily introduce registration issues - in fact it already happened and believe me it is nontrivial to investigate why client host fails to register to Capsule (if trying to connect to port 443 that sounds logically correct but wrong due to wrong rhsm.conf setting).

Moving the listening port back to 443 will gain these pros:

• logical coherence where any client machine within Satellite deployment registers to - this prevents misconfiguration issues due to lack of knowing the exception / rule with port 8443
• simplified firewall setting
• simplified POSTIN script in katello-ca-consumer RPM

Version-Release number of selected component (if applicable):
Sat 6.1.4 (i fact any Sat6)

How reproducible:
100%

Steps to Reproduce:
1. Install Sat, Caps, register content host to Sat and to Caps
2. Check what port the clients use for RHSM communication (i.e. rhsm.conf on clients)

Actual results:
clients registered to Sat talk via port 443
clients registered to Caps talk via port 8443

Expected results:
any client to talk to its "server" (Sat or Caps) via port 443

Additional info:
Once implemented, documentation needs to be updated - at least firewall setting