Bug #11185: "compliance" user role is broken - Rudder - Issue Tracker

Actions

Copy link

Bug #11185

closed

"compliance" user role is broken

Added by Alexis Mousset over 7 years ago. Updated about 7 years ago.

Status:

Released

Priority:

N/A

Assignee:

François ARMAND

Category:

Target version:

3.1.23

Pull Request:

https://github.com/Normation/rudder/p...

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:

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.

Actions

Copy link

Updated by Vincent MEMBRÉ over 7 years ago

Can you try to add read_configuration too ?

Actions

Copy link

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.

Actions

Copy link

Updated by Vincent MEMBRÉ over 7 years ago

Target version changed from 4.2.0~beta3 to 4.2.0~rc1

Actions

Copy link

Updated by Benoît PECCATTE over 7 years ago

Severity set to Major - prevents use of part of Rudder | no simple workaround
User visibility set to Operational - other Techniques | Technique editor | Rudder settings
Priority changed from 0 to 52