Project

General

Profile

Bug #12585

Custom acl are not parsed by api account API

Added by Vincent MEMBRÉ 7 months ago. Updated 6 months ago.

Status:
Released
Priority:
N/A
Category:
API
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

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 ]
}

Related issues

Related to Rudder - Bug #12476: Unhelpful log entry when enabling/disabling an API account Rejected

Associated revisions

Revision 8b85dfb0 (diff)
Added by Vincent MEMBRÉ 7 months ago

Fixes #12585: Custom acl are not parsed by api account API

History

#1 Updated by Vincent MEMBRÉ 7 months ago

  • Project changed from Private plugins common to Rudder
  • Category set to API
  • Target version set to 4.3.2

#2 Updated by Vincent MEMBRÉ 7 months ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ

#3 Updated by Vincent MEMBRÉ 7 months 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

#4 Updated by Vincent MEMBRÉ 7 months ago

  • Status changed from Pending technical review to Pending release

#5 Updated by Vincent MEMBRÉ 6 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.3.2 which was released today.

#6 Updated by Vincent MEMBRÉ about 1 month ago

  • Related to Bug #12476: Unhelpful log entry when enabling/disabling an API account added

Also available in: Atom PDF