Actions
Bug #25003
closedUser with node_all permission can't modify node policy mode
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
Rudder version : 8.1.4~git202406112319-debian11
When a user is declared as
<user role="node_all,read_only" password="LDAP" name="johndoe"/>
or
<user role="node_all" password="LDAP" name="johndoe"/>
in
/opt/rudder/etc/rudder-users.xml
, he doesn't have permission to change a node policy mode.
In Rudder 7.3, this was possible. After checking the 8.3 documentation, I didn't find any change in the permissions system that could explain this.
Regards,
Updated by François ARMAND 6 months ago
- Target version set to 8.1.4
- Severity set to Minor - inconvenience | misleading | easy workaround
Can confirm the problem.
The check is done on node_write
, so node_all
should provide it, so clearly a bug.
Updated by François ARMAND 6 months ago
- Target version changed from 8.1.4 to 8.0.10
OK, seems to be here since 8.0 actually
Updated by François ARMAND 6 months ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND 6 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Clark ANDRIANASOLO
- Pull Request set to https://github.com/Normation/rudder/pull/5723
Updated by Maxime Mérian 6 months ago
In our version, seems like a user vith node_read,node_write,read_only
permissions can't change a node policy mode.
If I understand what François said, it should be the case
Updated by Anonymous 6 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|26f900bf51488f78b7bc607f5f0e86fc6c845972.
Updated by Clark ANDRIANASOLO 6 months ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ 6 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.0.10 and 8.1.5 which were released today.
Actions