Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
I have an issue based around package and configuration file management within Satellite.
I would like all application area's to use Satellite to manage their software (Non OS products or specific ones) and configuration files .. and don't want them to have access to the main OS packages etc.. This would give BA great benefits particularly round the Sarbannes Oxley compliance that we have to achieve.. I can't see a way to do it with the current release without making things so complex ie: A satellite server for every application ! - so not a solution.
I would like to be able to give "application owners" control of their configuration files that are deployed by satellite. I may also like to give them access so that they can control the uploading of their own RPM's and subsequent deployment to "their" servers. What I don't want the "application area" to have access to the OS RPM's or configuration files.
Eg: we create a "Config channel" for each application and I would like them to be able to manage the config channel for themselves but nothing else within Satellite. The current control means that you have to give them org admin rights and this is way to high level. I hope this is a more indepth explanation. I believe that other companies have requested this functionality and it has also been escalated by some of your consultants.
This event sent from IssueTracker by tdunnon [SEG - Feature Request]
issue 121856
The RBAC model in Satellite 6.0, and the use of orgs, environments, and content views, should meet the requiremenets which you have stated above. When Satellite 6 comes out, please verify your scenarios. If they are not met please feel free to re-open this bug or open new specific RFE requests against Satellite6 features.