Bug 2221794

Summary:	Installer doesn't provide a way to configure trusted_proxies in Foreman's settings.yaml
Product:	Red Hat Satellite	Reporter:	Ewoud Kohl van Wijngaarden <ekohlvan>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED EOL	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	6.11.5	CC:	ehelms, gsulliva, zuansorg
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-01-22 17:03:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2170435

Description Ewoud Kohl van Wijngaarden 2023-07-10 19:08:58 UTC

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.

Comment 1 Bryan Kearney 2023-07-10 20:03:22 UTC

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