Bug 772742 - DB upgrade gives "All Resources Role" an unintended permission
Summary: DB upgrade gives "All Resources Role" an unintended permission
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Database
Version: 4.2
Hardware: All
OS: All
high
medium
Target Milestone: ---
: RHQ 4.3.0
Assignee: Jay Shaughnessy
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: jon30-sprint10, rhq43-sprint10 785987
TreeView+ depends on / blocked
 
Reported: 2012-01-09 20:36 UTC by Jay Shaughnessy
Modified: 2013-08-31 10:09 UTC (History)
1 user (show)

Fixed In Version: 4.3
Clone Of:
: 785987 (view as bug list)
Environment:
Last Closed: 2013-08-31 10:09:19 UTC
Embargoed:

Attachments (Terms of Use)
All Resources JON 2.4.2 (56.66 KB, image/png)
2012-02-09 16:56 UTC, Mike Foley 		no flags Details
All Resources JON 3.01 (99.34 KB, image/png)
2012-02-09 16:57 UTC, Mike Foley 		no flags Details
View All

Description Jay Shaughnessy 2012-01-09 20:36:57 UTC 
Upgrades to RHQ 4.3 mistakenly granted manage_repository perm to
'All Resources Role'.
Comment 2 Jay Shaughnessy 2012-01-09 20:48:18 UTC 
master commit c6706aed03df889e23102ea254b2d342141d8b9b

Fix the upgrade step that grants the bad permission. And add a new
step to revoke it if it exists.
Comment 3 Charles Crouch 2012-01-31 23:47:07 UTC 
Commits for this BZ went into master so setting target release to RHQ4.3
Comment 4 Mike Foley 2012-02-09 16:54:52 UTC 
documenting the verification with screenshots of role permissions in JON 2.4.2 upgraded to JON 3.01
Comment 5 Mike Foley 2012-02-09 16:56:53 UTC 
Created attachment 560662 [details]
All Resources JON 2.4.2
Comment 6 Mike Foley 2012-02-09 16:57:30 UTC 
Created attachment 560663 [details]
All Resources JON 3.01
Comment 7 Mike Foley 2012-02-09 17:15:54 UTC 
i logged this new BZ as part of the verification process

https://bugzilla.redhat.com/show_bug.cgi?id=789069
Comment 8 Heiko W. Rupp 2013-08-31 10:09:19 UTC 
Bulk close of old bugs in VERIFIED state.
Note You need to log in before you can comment on or make changes to this bug.