The basic problem here is that for a single resource, the Operations tab when the user doesn't have permission, should disable the operations links and show a message that the user doesn't have permission. This is already implemented for groups.
<jweiss> ghinkle: i'm also noticing a strange discrepancy between the operation tab of the group top level resource (AS Servers) and a single AS Server's Operation tab. in the group, the tab shows "You do not have permissions to execute operations on this group " and the links are disabled. the single resource has no such message, the links are enabled, and when you click them you get a message about not having permission.
the former seems like the proper way to deny permission on the op tab. why 2 implementations?
wait, what i mean is not, 'why do the internals require 2 impls', but rather even if there are two internal impls, why do they look different in the UI
<ghinkle> jweiss: i haven't gotten around to fixing the resource version... just the group version
<jweiss> ghinkle: ok, is there a jira for it? i'm not going to push for fixing in 2.2 but needs to be tracked
<ghinkle> not sure
<jweiss> i'll write one if i can't find it
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1984
This was JSF. Authz is done for the coregui resource and group Operations tabs. Specifically, the various buttons - New, Delete, etc. - are disabled if the user does not have the CONTROL perm.