Actions
Bug #12585
closed
Custom acl are not parsed by api account API
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
If you pass an aclList parameters to the request of api account, that parameter will be ignored and the list of acl authorized will be empty.
We need to add a parsing of that json data, which looks like this:
{
path : "/path/to/endpoint
verbs: [ HTTPVERB list ]
}
Updated by Vincent MEMBRÉ over 6 years ago
- Project changed from 53 to Rudder
- Category set to API
- Target version set to 4.3.2
Updated by Vincent MEMBRÉ over 6 years ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ over 6 years ago
- 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/1927
Updated by Vincent MEMBRÉ over 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|8b85dfb066619871b4080427088562f09b59893d.
Updated by Vincent MEMBRÉ over 6 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.2 which was released today.
- 4.3.2: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Vincent MEMBRÉ about 6 years ago
- Related to Bug #12476: Unhelpful log entry when enabling/disabling an API account added
Actions