Actions
Bug #11185
closed
"compliance" user role is broken
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Priority:
68
Name check:
Fix check:
Regression:
Description
I want to create a user account that has read only access to compliance information, but could not get it working.
I tried the "compliance" role that gives to access at all, and a "node_read,group_read,rule_read,directive_read" perm, but that only gave access to nodes.
Updated by Vincent MEMBRÉ over 7 years ago
Can you try to add read_configuration too ?
Updated by Alexis Mousset over 7 years ago
- Subject changed from Impossible to get read only access to compliance to "compliance" role is broken
It works! Thanks!
The only problem left is the broken "compliance" role.
Updated by 
Updated by
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/1727
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|3ce4b277c098067d6d146cb4a95ebd4dda2e9127.
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from Pending release to Released
Actions