Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2143051 - edit_organization permissions needed on upstream satellite
Summary: edit_organization permissions needed on upstream satellite
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Inter Satellite Sync
Version: 6.11.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.14.0
Assignee: Partha Aji
QA Contact: Sam Bible
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-15 22:13 UTC by Calvin Smith
Modified: 2023-11-08 14:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-08 14:18:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36503 0 Normal Closed edit_organization permissions needed on upstream satellite 2023-06-16 09:25:18 UTC
Red Hat Issue Tracker SAT-17023 0 None None None 2023-04-10 13:13:58 UTC
Red Hat Product Errata RHSA-2023:6818 0 None None None 2023-11-08 14:18:18 UTC

Description Calvin Smith 2022-11-15 22:13:56 UTC 
Description of problem:
The documentation around ISS says that the downstream satellite's credentials needs edit_organization permissions to download the certificate

Version-Release number of selected component (if applicable):
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/installing_satellite_server_in_a_disconnected_network_environment/index#configuring-server-to-synchronize-content-over-a-network_satellite

How reproducible:
Every time

Why is this OK and is there a workaround for customers that do not want to give downstream owners edit_organization permissions
Comment 1 Brad Buckingham 2022-12-08 13:54:15 UTC 
Hi Partha,

Do you happen to know why downloading the CA certificate requires the edit_organization permission? (See referenced doc link)

Does it provide more than the ability to retrieve/view content?

Thanks!
Comment 2 Partha Aji 2023-04-06 19:36:40 UTC 
There are 2 parts to the access here
1) To access the apache instance on the upstream you need the contents of https://<upstream-fqdn>/pub/katello-server-ca.crt
2) To access the RH repo contents itself you need the upstream organization's debug certificate. 

I  tested this and it seems odd but I really needed edit organization to download an organizations Debug Certificate (my guess is because it needs to be able to create a debug certificate if its not already there.) Will try to fix this.
Comment 3 Partha Aji 2023-06-13 04:30:27 UTC 
Connecting redmine issue https://projects.theforeman.org/issues/36503 from this bug
Comment 4 Bryan Kearney 2023-06-13 08:02:36 UTC 
Upstream bug assigned to paji
Comment 5 Bryan Kearney 2023-06-13 08:02:38 UTC 
Upstream bug assigned to paji
Comment 6 Bryan Kearney 2023-06-15 16:02:32 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36503 has been resolved.
Comment 9 Sam Bible 2023-10-03 17:23:02 UTC 
Verified on: 6.14 - Snap 18

Steps to Verify:
1. Create 2 Satellites, one downstream and one upstream
2. Create a role on the upstream satellite, with the following permissions:
   view_organizations
   view_products
   view_lifecycle_environments
   view_content_views
   export_content
3. Follow the instructions for Network Content Sync here:https://docs.theforeman.org/nightly/Managing_Content/index-katello.html#configuring-server-to-synchronize-content-over-a-network_content-management
4. Attempt to enable a few different repos on the downstream satellite.

Expected Results:
You are able to successfully setup Network CDN, and successfully enable the repositories synced on the upstream Satellite.

Actual Results:
You are able to successfully setup Network CDN, and successfully enable the repositories synced on the upstream Satellite.
Comment 12 errata-xmlrpc 2023-11-08 14:18:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.14 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:6818
Note You need to log in before you can comment on or make changes to this bug.