Architecture #24872
closed
Rework api authorization models
Added by Vincent MEMBRÉ about 1 year ago.
Updated 3 months ago.
Description
We tend to forget to define api authorisations. These could be avoided by forcing the type system to ensure we have an authorisation defined for each api.
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5669
- Target version changed from 8.0.9 to 8.2.0~alpha1
- Target version changed from 8.2.0~alpha1 to 8.3.0~alpha1
- Target version changed from 8.3.0~alpha1 to 8.3.0~beta1
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.3.0~beta1 which was released today.
- Related to Bug #26602: User with "compliance" perm get error on group, directive pages added
- Related to Bug #26690: User with limited rights gets Ajax error added
- Related to Bug #26843: User with 'user' role cannot get token status added
Also available in: Atom
PDF