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 1255777 - [RFE] Role Filters Limited By either Location or Lifecycle Environment
Summary: [RFE] Role Filters Limited By either Location or Lifecycle Environment
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Users & Roles
Version: 6.1.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 260381
TreeView+ depends on / blocked
 
Reported: 2015-08-21 14:21 UTC by joel.davis
Modified: 2019-09-26 13:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-21 11:40:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description joel.davis 2015-08-21 14:21:13 UTC
Description of problem:
We're wanting to implement a sort of self-service option for business units that want to manage their own patches or use the Satellite to deploy actions to their particular set of hosts. The names won't necessarily follow our normal naming convention (they were absorbed, hence the devolved status of patching) so matching on name won't work and we're all within the same organization so matching on organization_id won't help either.

They do have their own unique location and lifecycle environment. Matching view_content_hosts, etc on location will probably be useful eventually but it seems like matching on lifecycle environment would be the more "correct" way of managing devolved responsibility in general so that's my preference.

If you need me to clarify what I'm asking for then feel free to ask.

Version-Release number of selected component (if applicable):
I'm currently on Satellite 6.1.1

How reproducible:
90% of the time it works every time.

Steps to Reproduce:
1. Go into Administer > Roles
2. Select the role you want to limit and go to the filters
3. Attempt to add a filter for resource type "Content Host"
4. Uncheck "Unlimited" and attempt to restrict role's access to just the relevant hosts

Actual results:
There is no option for limit in such a way. Only by name or organization_id

Expected results:
Some options for more granular limiting of authority such as by Location, Lifecycle Environment, or membership in a particular Host Collection.

Comment 1 Daniel Lobato Garcia 2017-11-21 11:40:26 UTC
Since 6.2, Content Hosts permissions are controlled through regular "Host" permissions. Therefore, lifecycle_environment_id, location, and many more fields are available on the search filter. Closing.


Note You need to log in before you can comment on or make changes to this bug.