Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

In Foreman 2.4.0 (https://projects.theforeman.org/issues/30779) ActionDispatch::RemoteIp middleware was implemented. That means any reverse proxy needs to be configured in trusted_proxies in settings.yaml. That file is managed in the installer, but only in Foreman 3.2.0 (https://projects.theforeman.org/issues/34089) the installer option was added.

Features such as registration rely on this being configured correctly.

I'm asking for a cherry pick back to 6.11 so users can configure this.

This came up in https://github.com/theforeman/foreman-documentation/pull/2219 and is blocking https://bugzilla.redhat.com/show_bug.cgi?id=2170435.

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34089 has been resolved.