Looking at this I think some additional work is needed.

First of all some background. In upstream we disabled the feature by default since the templates feature (on which it depends) is not enabled.

However, in the downstream Capsule scenario the templates feature is enabled by default. That means we could enable registration by default. That means the instructions for users would be easier, essentially it should work out of the box.

Just to be clear, we don't enable this on the Satellite scenario since AFAIK there is no benefit. However, I may be missing something and in that case, I'd be open to doing so.

How do we approach this process wise? Open a new BZ to track enabling by default?

Changing this to an installer bug. I think it should be merged before 7.0.0.

Hello Ewoud,

I will try to answer this part

Just to be clear, we don't enable this on the Satellite scenario since AFAIK there is no benefit. However, I may be missing something and in that case, I'd be open to doing so.
>>> This is particularly for customers who has *single* Satellite deployed for managing content hosts. I believe there is no harm or unintended side-effects if we enabled by default on Satellite.

AFAIK you can use the registration feature directly on Foreman and you don't need it on the Smart Proxy. It would only a layer of indirection. However, I haven't checked this recently.

And the harm would be that you do get the templates feature enabled, which means you can have added confusion. Suddenly you may need to select a templates proxy where there is only one option. It would require enabling HTTP and opening port 8000 on the Satellite server. Those are much bigger changes.

Verified this with satellite capsule Satellite 7.0 and Snap 16. Both are getting enabled after adding a smart proxy.   

[root@ ~]# satellite-installer --full-help | grep -E '\-\-foreman.*proxy.*registration |\-\-foreman.*proxy\-templates '
    --foreman-proxy-registration  Enable Registration feature (current: true)
    --foreman-proxy-templates     Enable templates feature (current: true) 

@ekohlvan I still see that the registration feature is not enabled by default from the installer settings which differs from the statement you added on https://bugzilla.redhat.com/show_bug.cgi?id=2054971#c10  

[root@ ~]# rpm -qa | grep satellite-7
satellite-7.0.0-0.7.beta.el7sat.noarch
[root@ ~]# satellite-installer --full-help | grep -E '\-\-foreman.*proxy.*registration |\-\-foreman.*proxy\-templates '
    --foreman-proxy-registration  Enable Registration feature (current: false)
    --foreman-proxy-templates     Enable templates feature (current: false)

My understanding was that if the registration feature is default enabled why it is not true? (It could be raised different bug for this)

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5498

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days