Bug 790489 - Permissions: read-only user cannot access Sync Management content
Summary: Permissions: read-only user cannot access Sync Management content
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
high
high vote
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-14 16:27 UTC by Corey Welton
Modified: 2019-09-26 13:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 18:27:04 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Corey Welton 2012-02-14 16:27:27 UTC
Description of problem:
If a user has read-only role, s/he cannot access the Sync Management tab/subtabs, even if 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Login as admin; create user 'reader' and grant builtin role "Read Everything" to this user.
2.  While still logged in as admin, create provider/product/repo, etc., and begin syncing
3.  Logout; Login as user 'reader'
4.  Attempt to access the "Content Management > Sync Management" tab and/or any of the underlying submenus.

  
Actual results:
Sync Management tab does not appear
User cannot access said menus.

Expected results:
read only user should be able to see and access these, just not modify anything.

Additional info:

Comment 2 Eric Helms 2012-02-23 21:08:22 UTC
ebf6e88f12d56e40e50fd98ac6559fd225d127ab

The read only role should now allow a user to see all three sync management pages - sync plans, sync schedule and sync status but only view details and status of items.

Comment 4 Corey Welton 2012-03-02 21:47:30 UTC
QA Verified 0.1.301-2.el6

Comment 6 Mike McCune 2013-08-16 18:13:27 UTC
getting rid of 6.0.0 version since that doesn't exist


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