Bug 724632 (BRMS-539) - Guvnor displays messages of permission denied unnecessarily
Summary: Guvnor displays messages of permission denied unnecessarily
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-539
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: 5.1.0 GA
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 5.1.0.PostGA
Assignee: Tihomir Surdilovic
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-21 14:15 UTC by Alessandro Lazarotti
Modified: 2011-03-17 17:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Fedora 12, JDk 1.6, BRMS 5.1
Last Closed: 2011-03-17 17:39:06 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-539 0 Major Closed Guvnor displays messages of permission denied unnecessarily 2013-08-26 03:28:31 UTC
Red Hat Issue Tracker GUVNOR-1163 0 Minor Resolved Guvnor displays messages of permission denied unnecessarily 2013-08-26 03:28:30 UTC

Description Alessandro Lazarotti 2011-01-21 14:15:25 UTC 
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000005iKiQ&sfdc.override=1
securitylevel_name: Public

A user logging in BRMS with fine grained role package.developer and attempting to create a new rule or new model, Guvnor display the message:
"Sorry, insufficient permissions to perform this action" (even though he has the necessary role), but he ignoring the message and continuing with the work, he can accomplish the task.
Comment 1 Alessandro Lazarotti 2011-01-21 14:16:50 UTC 
Link: Added: This issue related GUVNOR-1163
Comment 2 Jordan Saunders 2011-01-21 14:38:34 UTC 
This issue occurs with package.admin also
Comment 3 Tihomir Surdilovic 2011-03-17 17:37:34 UTC 
I have added a fix for package.admin and package.developer users to be able to create the default repository now. The error messages come from the fact that each of your users also need package.admin / package.developer permissions on the targeted package AND also the globalArea. When you administer users please make sure that they also have same permissions on globalArea as well.
Comment 4 Tihomir Surdilovic 2011-03-17 17:38:48 UTC 
A package can use rules, and other resources that were promoted to the globalArea and as such it is needed that all users also have necessary permissions on globalArea as well.
Note You need to log in before you can comment on or make changes to this bug.