Test that the measurement permission works. I think the only thing this gives you permission to do is to change the collection intervals for metric schedules. Someone correct me if I'm wrong. Who ever is assigned to this needs to check the code to make sure I'm right.
1) Created 'Everything' group including all discovered resources(See parent issue for details). 2) Create two additional user accounts i) u:none with no role perms and member of everything group. ii)u:measure w/ 'measure' perms and member of 'Everything' 3) Logged into the app from three separate browsers(FFx2 & IE) with three separate accounts Following results obtained while viewing/testing " Logged in-> Resources -> Platforms->[Select One] -> Click on [Free Memory]. At the bottom of the page focus on modifying one of the properties under 'Metric Baseline & Expected Range ': #u:none - details shown but NO 'Change Value' link is available. #u:measure - details shown and ABLE to edit/change the 'High Range' and successfully persist to JON inventory. #u:rhqadmin - details shown and ABLE to edit/change the 'High Range' and successfully persist to JON inventory. Also checked to see if the edit url could be accessed from the user 'none', but errored out and doesn't appear to be enough context from url anyway. Ex. Use http://127.0.0.1:7080/resource/common/monitor/visibility/ViewChart.do The 'none' user could NOT see the edit page link correctly. SUMMARY: working as expected.
Added one more level of restricted visibility group testing due to changes in group authorization mechanism. See parent issue for more detailed description. In addition to above, also created: i) Recursive group that included the Platform only. ii) Role that included group from first step and only 'measure' perms selected. ii) User attached to role. Works as expected.
Nothing additional to report.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1863