Bug #32622
RHEL content on a content proxy returns a 403 to clients
Pull request:
Fixed in Releases:
Found in Releases:
Description
Discourse thread: https://community.theforeman.org/t/403-forbidden-error-for-rhel-repos-with-the-clients-registered-to-smart-proxy/23450
[root@rhel7-client entitlement]# curl --cert /etc/pki/entitlement/1373568910360318289.pem --key /etc/pki/entitlement/1373568910360318289-key.pem https://ForemanSmartProxy.example.com/pulp/content/ORG/DEV/RHEL_7/content/dist/rhel/server/7/7Server /x86_64/os/repodata/repomd.xml 403: A client certificate was not received via the `X-CLIENT-CERT` header.
Associated revisions
History
#1
Updated by The Foreman Bot about 1 year ago
Updated by - Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/puppet-pulpcore/pull/193 added
#2
Updated by Eric Helms about 1 year ago
Updated by - Target version set to 2.3.4
I am proposing this for 2.3.4 and 2.4 as it is affecting a number of users.
#3
Updated by Eric Helms about 1 year ago
- Bugzilla link set to 1961885
#4
Updated by The Foreman Bot about 1 year ago
- Pull request https://github.com/theforeman/puppet-pulpcore/pull/191 added
#5
Updated by Eric Helms about 1 year ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-pulpcore|627f084160634a18b04a250546e8a671265b944f.
#6
Updated by Amit Upadhye about 1 year ago
Updated by - Fixed in Releases 2.3.4 added
Fixes #32622: Include StdEnvVars, ExportCertData SSL options in Apache
When deploying a stand-alone vhost, Pulp needs these SSL options
set in order for X-CLIENT-CERT to be set.