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 1417824 - [RFE] Multitenancy Support for puppet classes
Summary: [RFE] Multitenancy Support for puppet classes
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Organizations and Locations
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-31 07:53 UTC by orabin
Modified: 2021-06-10 11:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-05 17:25:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description orabin 2017-01-31 07:53:53 UTC
Description of problem:
Puppet classes are not connected to organizations so a user from organization A can see and edit smart class parameters and smart variables created by a user from organization B.

Steps to Reproduce:
1. Create user A with permissions to organization A only
2. Create user B with permissions to organization B only
3. Log in as user A, go to Configure -> Classes and edit a puppet class
4. Add a smart variable
5. Log in as user B, go to Configure -> Classes and edit the same puppet class
6. Go to Smart Variables tab

Actual results:
The smart variable added by user A is visible and can be edited


Expected results:
The smart variable added by user A is hidden because the user is not in organization A


Additional info:

Comment 4 Bryan Kearney 2017-10-05 17:25:50 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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