I wrote a paper in April this year discussing the different functionality available to users with different roles - "Crafting Zenoss Core users for events and zProperties", available from docs/DOC-3561 .The paper was written with Zenoss Core 2.3.2.
I have been revisiting the content of the paper with Zenoss Core 2.5.1 and find significant differences:
Zenoss 2.3.2
| Zenoss 2.5.1
|
|---|
| ZenUser role has no left-hand Event Console | ZenUser role does see left-hand Event Console |
| ZenUser role cannot Ack or Close events by default | ZenUser role can Ack & Close events by default |
| ZenUser role cannot add to event Log | ZenUser role can add to event Log |
Event View defined for a Group not inherited by users in that Group | Event View defined for a Group not inherited by users in that Group (ie no change but is this a bug?) |
Adminstered Objects defined for a Group are inherited by users in that Group | Adminstered Objects defined for a Group are NOT inherited by users in that Group (is this a bug?) |
From http://zenoss:8080/zport/manage_access , Manage Events not explicitly granted to any role | From http://zenoss:8080/zport/manage_access , Manage Events explicitly granted to Manager, Ownner and ZenManager, but NOT to ZenUser |
| Not checked in 2.3.2 | ownerid field in an event updated with latest user to Ack / Close. Not updated by Log updates. (regardless of role) |
| |
| |
| |
I guess my main question is "are these changes deliberate or is it a bug that the Zope roles no longer seem to apply to the new event console?"
The 2 aspects of configuring Group privileges not being inherited by users in that group DO seem like bugs - why else have Groups?
Anyone else have observations or comments? I'll open ticket(s) if we think these are bugs.
Cheers,
Jane
