Bug 1276769

Summary: [RFE] RBAC Control create_repository
Product: Red Hat Satellite Reporter: Karl Abbott <kabbott>
Component: Users & RolesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.3CC: andrew.schofield, bkearney, oprazak, sauchter
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-18 17:49:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1316897    

Description Karl Abbott 2015-10-30 20:05:40 UTC 
What problem/issue/behavior are you having trouble with?  What do you expect to see?

Within the 'Product and Repositories'  RBAC Resource type, there are options to view, create, edit, destroy and sync products. However there do not seem to be any controls to allow the same actions for repositories. 

We are permissioning users and teams to their own Product. We want to allow users to be able to CREATE their own repositories in this product but DENY them the ability to CREATE products.

(Products / Repositories seem to share the same permissions?).

I want to see the:

view_repositories
create_repositories
edit_repositories
destroy_repositories

Permissions so that users can create / modify repositories they have access to but be denied the ability to create more products.
Comment 3 Bryan Kearney 2016-07-08 20:22:22 UTC 
Per 6.3 planning, moving out non acked bugs to the backlog
Comment 6 Ondřej Pražák 2017-01-18 14:05:21 UTC 
Created redmine issue http://projects.theforeman.org/issues/18133 from this bug
Comment 7 Bryan Kearney 2018-07-18 17:49:45 UTC 

*** This bug has been marked as a duplicate of bug 1410916 ***