Actions
Bug #37308
closedREMOTE_USER is unset by Apache for Pulpcore Registry when it shouldn't be
Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
Difficulty:
Triaged:
Yes
Description
Any calls to /pulpcore_registry/v2/ lose REMOTE_USER in the headers. This header is necessary to authenticate with Pulp to push container content.
To work around it, I removed every reference to setting / unsetting REMOTE_USER in /etc/httpd/conf.d/05-foreman-ssl.conf and added `RequestHeader set REMOTE_USER "admin"`. Only then did the REMOTE_USER header get sent to Pulp.
Updated by The Foreman Bot 9 months ago
- Status changed from New to Ready For Testing
- Assignee set to Ian Ballou
- Pull request https://github.com/theforeman/puppet-pulpcore/pull/337 added
Updated by Anonymous 8 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-pulpcore|21aa39e28f19b40bf328ebba514465fb9cfb9fe2.
Updated by Ewoud Kohl van Wijngaarden 6 months ago
- Subject changed from Fix apache config so REMOTE_USER is not unset for pulpcore registry to REMOTE_USER is unset by Apache for Pulpcore Registry when it shouldn't be
- Triaged changed from No to Yes
Actions