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 1346352 - On upgraded Satellite Viewer role user still can manage Content Views
Summary: On upgraded Satellite Viewer role user still can manage Content Views
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Zach Huntington-Meath
QA Contact: Lukas Pramuk
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1335807
TreeView+ depends on / blocked
 
Reported: 2016-06-14 15:25 UTC by Lukas Pramuk
Modified: 2019-09-26 14:48 UTC (History)
3 users (show)

Fixed In Version: rubygem-katello-3.0.0.53-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:42:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15460 0 None None None 2016-06-20 01:03:17 UTC

Description Lukas Pramuk 2016-06-14 15:25:10 UTC 
Description of problem:
On upgraded Satellite Viewer role user still can manage Content Views.
as BZ 1341656 fixed only fresh Satellite installation.

With upgrades it's a bit tricky, the above fix avoids to modify existing roles filters as they can be already modified by Satellite admin. But still I would at least remove all perms that was wrongly matched on Sat6.1 as no one (read no customer) would expect/set Viewer role to have managing perms...

Version-Release number of selected component (if applicable):
Sat6.2.0-Snap15.1

How reproducible:
always

Steps to Reproduce:
1. Upgrade satellite
2. Prepare some content, some CVs under admin account
3. Create a user with just Viewer role assigned
4. Login as viewer user and navigate to Content -> Content Views
5. Have a "good play" with admin content

Actual results:
wrongly assigned perms to Viewer role from Sat6.1 still persists on Sat6.2

Expected results:
wrongly assigned perms to Viewer role dont persist on Sat6.2

Additional info:
can be workarounded: remove all filters that dont match "^view_*" from Viewer role.
Comment 2 Zach Huntington-Meath 2016-06-20 00:12:33 UTC 
Created redmine issue http://projects.theforeman.org/issues/15460 from this bug
Comment 3 Brad Buckingham 2016-06-21 15:08:25 UTC 
Moving to assigned based on existence of PR.
Comment 4 Brad Buckingham 2016-06-24 19:27:07 UTC 
Moving to POST since upstream PR has been merged.
Comment 5 Lukas Pramuk 2016-07-12 11:07:38 UTC 
VERIFIED.

@satellite-6.2.0-19.1.el6sat.noarch
tfm-rubygem-katello-3.0.0.58-1.el6sat.noarch

used manual reproducer in comment #0

>>> viewer role user is no longer able to manage content-views even on upgraded Satellite
Comment 6 Bryan Kearney 2016-07-27 11:42:49 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501
Note You need to log in before you can comment on or make changes to this bug.