Description of problem:

As explained in https://bugzilla.redhat.com/show_bug.cgi?id=2247445 right now, If I want to use GRT and register a system with the Satellite server directly then, I need to ensure that the system can connect both on port 443 as well as 80 of the satellite.

But if someone is not using satellite for provisioning at all, They would want an incoming connection on port 80 to be disabled for security reasons. And that would cause the registration to fail at the end.

This is because, at the very end of registration, This API "GET /unattended/built?token=<token here>" is executed to update the build status of the host and it always targets port 80 of the satellite over HTTP.

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

Any Supported version of Satellite ( 6.11 - 6.14 )

How reproducible:

Always and Easily

Steps to Reproduce:
1. Install and Configure a Satellite so that a system can be registered with it.
2. Block incoming access on port 80 of the satellite
3. Try registering a host with the satellite via the GRT method and observe till the end.

Actual results:

• Host is registered fine and yum is working as well
• The Host never came out of Build mode because the `/unattended/built` endpoint failed to execute.
• Due to this, No facts would be updated for the host going forward unless someone manually cancels the build.

Expected results:

No registration method ( including GRT ) should depend on access of port 80 , whether it's satellite or capsule.

Additional info:

As explained in https://bugzilla.redhat.com/show_bug.cgi?id=2247445, we don't have this issue for external capsules, as there we use port 8000 to hit the `/unattended/built` endpoint

Perhaps we can make it mandatory to enable templates capsule in Satellite as well and make use of port 8000 instead or develop some other solution that can work over port 443.