Bug 697855 - Reports->Configuration History: User without configure read permissions can view a config history of a resource in reports
Summary: Reports->Configuration History: User without configure read permissions can v...
Keywords:
Status: CLOSED DUPLICATE of bug 696648
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: rhq4
TreeView+ depends on / blocked
 
Reported: 2011-04-19 13:07 UTC by Sunil Kondkar
Modified: 2011-10-04 19:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-19 19:48:11 UTC


Attachments (Terms of Use)

Description Sunil Kondkar 2011-04-19 13:07:10 UTC
Description of problem:
User without configure read permissions can view a config history of a resource in Reports->Configuration History page.

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

build#1144 (Version: 4.0.0-SNAPSHOT Build Number: 50f58a4)


How reproducible:

Always

Steps to Reproduce:

1. Login to RHQ as rhqadmin.
2. Create a user and a compatible group of resorces (Ex: RHQ Agent).
3. Create a role with no permissions.
4. Assign the resource group and the user created to the role.
5. Logout and login as the user created above( with no permissions)
6. Navigate to Reports->Configuration History.

  
Actual results:
The Reports->Configuration History displays the config history rows for the resource(RHQ Agent)


Expected results:
User without configure read permissions should not be able to view config history of a resource.

Additional info:
When the same user (without configure read permissions) navigates to the individual resource, the 'Configuration' tab is disabled as expected.

Comment 1 Jay Shaughnessy 2011-04-19 19:48:11 UTC
This issue was already solved. Marking as duplicate.

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


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