Project

General

Profile

Actions

Bug #37308

closed

REMOTE_USER is unset by Apache for Pulpcore Registry when it shouldn't be

Added by Ian Ballou 4 months ago. Updated 23 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

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.

Actions #1

Updated by The Foreman Bot 4 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
Actions #2

Updated by The Foreman Bot 3 months ago

  • Fixed in Releases 3.11.0 added
Actions #3

Updated by Anonymous 3 months ago

  • Status changed from Ready For Testing to Closed
Actions #4

Updated by Ewoud Kohl van Wijngaarden 23 days 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

Also available in: Atom PDF