Project

General

Profile

Actions

Bug #12585

closed

Custom acl are not parsed by api account API

Added by Vincent MEMBRÉ almost 3 years ago. Updated almost 3 years 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 RejectedVincent MEMBRÉActions
Actions #1

Updated by Vincent MEMBRÉ almost 3 years ago

  • Project changed from 53 to Rudder
  • Category set to API
  • Target version set to 4.3.2
Actions #2

Updated by Vincent MEMBRÉ almost 3 years ago

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

Updated by Vincent MEMBRÉ almost 3 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
Actions #4

Updated by Vincent MEMBRÉ almost 3 years ago

  • Status changed from Pending technical review to Pending release
Actions #5

Updated by Vincent MEMBRÉ almost 3 years ago

  • Status changed from Pending release to Released

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

Actions #6

Updated by Vincent MEMBRÉ over 2 years ago

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

Also available in: Atom PDF