Escalated to Bugzilla from IssueTracker
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]
this is not a usability bug. it is a feature request. reassigning to feature queue.
*** Bug 248383 has been marked as a duplicate of this bug. ***
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.