Actions
Bug #27085
open
Change validation acceptation and decline endpoints fail with permission issues
Status:
Pending technical review
Priority:
N/A
Assignee:
Target version:
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Small
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
Because of the same issue as in #26605, and since we rewrote all effects into ZIO, we now have the issue when checking user rights, which should be initialized in the API.
The consequence is not being able to accept or decline a change request from the API, even as admin user.
Updated by Clark ANDRIANASOLO 2 days ago
- Related to Bug #26605: CurrentUser.queryContext is null when used in a ZIO for added
- Related to Architecture #26714: Migrate WorkflowService to use ZIO added
Updated by Clark ANDRIANASOLO 2 days ago
- Status changed from New to In progress
- Assignee set to Clark ANDRIANASOLO
Updated by Clark ANDRIANASOLO 2 days ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to Véronique HAYAERT
- Pull Request set to https://github.com/Normation/rudder-plugins/pull/852
Actions