Project

General

Profile

Actions

Bug #26539

open

API account json for ACL is misleading and cumbersome and missing token deletion

Added by François ARMAND 19 days ago. Updated 9 days ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
API
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

Currently, when we want to add an API account with ACL with GET, POST on "some/url", we need to use:

...
{ "acl" : [ {"verb": "GET", "path": "some/url"}, {"verb": "POST", "path": "some/url" } ]
...

If the path are not correctly sorted, we can really miss what we are doing, plus it's cumbersome to write and space inefficient.
We want:

...
{ "acl" : [ {"verbs": "GET,POST", "path": "some/url"} ]
...

We verbs is non-empty (else ignored), and when it's on response, rudder merge correctly things.

Also, we want to be able to delete a token, not just regenerate one, so we need to change that REST endpoint:

- POST / "apiaccounts" / "{id}" / "regenerate" 

To than couple, adding "token" for clarity of semantic:

- POST / "apiaccounts" / "{id}" / "token" / "regenerate" 
- DELETE / "apiaccounts" / "{id}" / "token" 
Actions #1

Updated by Raphael GAUTHIER 12 days ago

  • Status changed from New to In progress
  • Assignee changed from François ARMAND to Raphael GAUTHIER
Actions #2

Updated by Raphael GAUTHIER 9 days ago

  • Status changed from In progress to New
  • Assignee deleted (Raphael GAUTHIER)
Actions

Also available in: Atom PDF