Project

General

Profile

Actions
Copy link

User story #5798

closed

Different access levels for API keys / REST API authorizations and rights

Added by Florian Heigl about 10 years ago. Updated almost 7 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
API
Target version:
4.3.0~rc1
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

It would be very very helpful to assign permissions to API keys.

  • The most important piece would being able to create ones that only have readonly access.
  • use normal user levels
  • allow accepting nodes only
  • allow access depending on origin of the caller (localhost, trusted networks, ...)

One very heartwarming bonus would be to be allowed to skip validation / change requests for API based accesses (by token)
Audit log doesn't need to be skippable ;)

Related issues 4 (1 open — 3 closed)

Related to Rudder - User story #6193: Add a command to create api tokenRejectedActions
Related to Rudder - User story #8183: Add a more detailed status API with component statusNewVincent MEMBRÉActions
Related to Rudder - User story #10678: REST Api authorization management by rolesRejectedActions
Is duplicate of Rudder - User story #5627: Readonly API or otherwise restrictable API AccountsReleasedFrançois ARMANDActions
Actions
Copy link
 #1

Updated by François ARMAND about 10 years ago

  • Assignee set to François ARMAND
  • Target version set to 3.0.0~beta1

Well, yes, of course.

The read only is a must have - no excuse for that.

The rights and change request things are nice, I will look about how to do that (in particular the one for validation skiping, it makes a lot of sense).

Actions
Copy link
 #2

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 3.0.0~beta1 to 3.1.0~beta1
Actions
Copy link
 #3

Updated by Benoît PECCATTE almost 10 years ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.1.0~beta1 to 3.1.0~rc1
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.1.0~rc1 to 3.1.0
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.1.0 to 3.1.1
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 3.1.1 to 3.1.2
Actions
Copy link
 #10

Updated by Jonathan CLARKE over 9 years ago

  • Target version changed from 3.1.2 to 3.2.0~beta1
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.2.0~beta1 to 3.2.0~rc1
Actions
Copy link
 #12

Updated by Benoît PECCATTE almost 9 years ago

  • Target version changed from 3.2.0~rc1 to 3.2.0~rc2
Actions
Copy link
 #13

Updated by Benoît PECCATTE almost 9 years ago

  • Target version changed from 3.2.0~rc2 to 3.2.0
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.2.0 to 3.2.1
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.2.1 to 3.2.2
Actions
Copy link
 #16

Updated by Alexis Mousset over 8 years ago

  • Target version changed from 3.2.2 to 4.0.0~rc2
Actions
Copy link
 #17

Updated by Janos Mattyasovszky over 8 years ago

  • Related to User story #8183: Add a more detailed status API with component status added
Actions
Copy link
 #18

Updated by François ARMAND over 8 years ago

  • Related to User story #5627: Readonly API or otherwise restrictable API Accounts added
Actions
Copy link
 #19

Updated by François ARMAND about 8 years ago

  • Target version changed from 4.0.0~rc2 to 4.1.0~beta1
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 4.1.0~beta1 to 4.1.0~beta2
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 4.1.0~beta2 to 4.1.0~beta3
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 4.1.0~beta3 to 4.1.0~rc1
Actions
Copy link
 #23

Updated by François ARMAND almost 8 years ago

  • Target version changed from 4.1.0~rc1 to 4.2.0~beta1
Actions
Copy link
 #24

Updated by François ARMAND over 7 years ago

  • Subject changed from Different access levels for API keys to Different access levels for API keys / REST API authorizations and rights
Actions
Copy link
 #25

Updated by François ARMAND over 7 years ago

Actions
Copy link
 #26

Updated by Alexis Mousset over 7 years ago

  • Target version changed from 4.2.0~beta1 to 4.2.0~beta2
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.2.0~beta2 to 4.2.0~beta3
Actions
Copy link
 #28

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.2.0~beta3 to 4.2.0~rc1
Actions
Copy link
 #29

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.2.0~rc1 to 4.2.0~rc2
Actions
Copy link
 #30

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.2.0~rc2 to 4.2.0
Actions
Copy link
 #31

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.2.0 to 4.2.1
Actions
Copy link
 #32

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.2.1 to 4.2.2
Actions
Copy link
 #33

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.2.2 to 4.2.3
Actions
Copy link
 #34

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.2.3 to 4.2.4
Actions
Copy link
 #35

Updated by François ARMAND almost 7 years ago

  • Status changed from New to Rejected
  • Assignee deleted (François ARMAND)
  • Target version changed from 4.2.4 to 4.3.0~rc1

Now that #5627 is implemented, we can tell that that one is actually a duplicate :)

Actions
Copy link
 #36

Updated by François ARMAND almost 7 years ago

  • Related to deleted (User story #5627: Readonly API or otherwise restrictable API Accounts)
Actions
Copy link
 #37

Updated by François ARMAND almost 7 years ago

  • Is duplicate of User story #5627: Readonly API or otherwise restrictable API Accounts added
Actions
Copy link

Also available in: Atom PDF