Actions
Enhancement #23014
closed
Remove "no access" permission in token authorization
Effort required:
Name check:
To do
Fix check:
Checked
Regression:
No
Description
It is redundant, useless and confuses the user
For the migration,
Files
Updated by François ARMAND 10 months ago
- File clipboard-202307061756-hisem.png clipboard-202307061756-hisem.png added
- Tracker changed from Bug to Enhancement
- Description updated (diff)
- Target version set to 7.3.4
- Priority deleted (
0)
Updated by François ARMAND 10 months ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND 10 months ago
- Description updated (diff)
Actually none is used as a bottom value in several computation/cases, so it can't be removed. We will just remove the "none" choice from the drop down.
It will achieve the goal of not confusing people.
If someone look-up a token with "none" in the admin UI, we will just translate it to "read-only & disable". The use will then choose to save that change or ignore/cancel.
Updated by François ARMAND 10 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/4873
Updated by Anonymous 10 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|21c7d7d2d94fcccfd6c438ddd9408ce22363d81d.
Updated by
Updated by Vincent MEMBRÉ 10 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.4 which was released today.
Actions