1) Log in as user with no config perms for an accessible resource that does have resource config history. 2) Nav to summary->activity (resource dash) for the resource 3) The resource config update history portlet will generate an excpetion The exception is server-side, a bad query is generated in the criteria fetch.
commit 18a3a539ccb069162b0d6d69c9cbf0f055f59205 Author: Jay Shaughnessy <jshaughn> Date: Fri Apr 15 15:38:28 2011 -0400 This seemed to be a flat out grammar issue in certain generated queries for non-permissioned users. Test Notes- test the scenario above as well as many other non-permissioned queries for resources and groups as possible.
Verified on build123 (Version: 4.1.0-SNAPSHOT Build Number: a6d2d56) Created a user and a resource group. Created a role with no config permissions and assigned the group and the user to the role. Logged in as the user with no config permissions and navigated to the summary->activity page for the resource. No exception is observed. Also verified this by navigating to the summary->activity page for the resource group. No exception is observed. Marking as verified.
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.