Actions
Bug #17712
closed
Missing branding API (and others?) in API authorizations
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
When other plugins are loaded with api authz plugin, all their API are listed in the list of restricted api. But that's not the case for branding, and perhaps others.
There is no obvious difference between branding (not listed) and datasources for ex (listed).
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1-1.7 to 6.1-1.8
Updated by François ARMAND over 4 years ago
- Subject changed from Missing branding API (and others?) to Missing branding API (and others?) in API authorizations
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 52
Updated by François ARMAND over 1 year ago
- Target version changed from 6.1-1.8 to 7.2
- Priority changed from 52 to 0
- Regression set to No
We forgot to declare the API in the plugin definition
Updated by François ARMAND over 1 year ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND over 1 year 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-plugins/pull/570
Updated by Anonymous over 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder:rudder-plugins|7627b1716065c49a2f01248e42e6a36270d385e8.
Updated by Alexis Mousset over 1 year ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ 7 months ago
- Status changed from Pending release to Released
Actions