Bug #17712
closed
Missing branding API (and others?) in API authorizations
Added by François ARMAND about 4 years ago.
Updated about 1 month ago.
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
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).
- Target version changed from 6.1-1.7 to 6.1-1.8
- 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
- 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
- Status changed from New to In progress
- Assignee set to François ARMAND
- 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
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Anonymous 
Updated by