Description of problem: Repository/RPMs can be accessed, browse and downloaded from the browser without even downloading the client certificate on the browser. Version-Release number of selected component (if applicable): 6.10 How reproducible: 100 % Steps to Reproduce: 1. Access the URL https://<satellite.example.com>/pulp/content/ or https://<capsule.example.com>/pulp/content/ in any browser. 2. We can see all the repos synced to the Satellite or capsule without downloading the client certificate. We can even download the packages as well. 3. We don't even require to login on the Satellite web UI for accessing these URL. Actual results: RPMs synced to the Satellite/capsule can be accessed or downloaded without client certificate on the browser. Expected results: This should give the error "Service Unavailable" the same as 6.9. Even with the client certificate on browser, it should also be required to login on the Satellite serve. Additional info:
Created redmine issue https://projects.theforeman.org/issues/34950 from this bug
*** Bug 2075752 has been marked as a duplicate of this bug. ***
With the change from Pulp 2 to Pulp 3 there was a change in behavior in how protection of repositories is handled. It is true that in the current implementation the list of repositories is viewable but the repository itself and the content within it are both not browsable or downloadable without a valid client certificate. We are examining further whether viewing the list of available repositories is something we can gate.
Given Pulp 3 handles cert guard differently than Pulp 2 did, this particular bug would need to be an RFE, something akin to "Prevent repositories that are protected by client certificates from appearing in the list of available repositories at /pulp/content". If that is something you would like to see, please do update this to an RFE and the text. Any additional context or use case information to help the guide the team would also be appreciated.
Upstream bug assigned to ehelms
Requesting needsinfo from upstream developer dkliban, ggainey because the 'FailedQA' flag is set.
Dropped the Pulp-related NEEDINFOs as the remaining changes are NOT in the pulp realm (but in the installer) and the Pulp bits have been verified to be working as expected.
foreman-installer 3.7.0 now defaults to HIDE_GUARDED_DISTRIBUTIONS=True (but overrideable by the user), so this should be the last missing bit. Moving to POST.
@pcreech why was this manually moved to ON_DEV? the fix is in foreman-installer-3.7.0-1 while we still only ship foreman-installer-3.7.0-0.4.rc3 in snap 5. additionally, foreman-proxy and foreman-selinux packages weren't updated to their respective GA versions either.
Verified: Verified with: - foreman-installer-3.7.0.1-1.el8sat.noarch - Satellite 6.14.0 snap 7 Test steps: - satellite-installer --scenario satellite --full-help |grep foreman-proxy-content-pulpcore-hide-guarded-distributions - Go to https://satellite.example.com/pulp/content/ Observations: - foreman-proxy-content-pulpcore-hide-guarded-distributions installer option is present and is enabled by default. - No content listed/downloadable on https://satellite.example.com/pulp/content/ - "403: [('PEM routines', 'get_name', 'no start line')]" when the setting is disabled. Additional info: # satellite-installer --full-help | grep foreman-proxy-content-pulpcore-hide-guarded-distributions --foreman-proxy-content-pulpcore-hide-guarded-distributions Hide distributions that are protected by a content guard from the default listing (current: true) --reset-foreman-proxy-content-pulpcore-hide-guarded-distributions Reset pulpcore_hide_guarded_distributions to the default value (true)