Project

General

Profile

User story #5798

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

Added by Florian Heigl over 5 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
API
Target version:
Pull Request:
Suggestion strength:
User visibility:
Effort required:

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

Related to Rudder - User story #6193: Add a command to create api tokenNewActions
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
#1

Updated by François ARMAND over 5 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).

#2

Updated by Jonathan CLARKE over 5 years ago

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

Updated by Benoît PECCATTE over 5 years ago

  • Description updated (diff)
#4

Updated by Vincent MEMBRÉ about 5 years ago

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

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.1.0~rc1 to 3.1.0
#8

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.1.0 to 3.1.1
#9

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.1.1 to 3.1.2
#10

Updated by Jonathan CLARKE almost 5 years ago

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

Updated by Vincent MEMBRÉ over 4 years ago

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

Updated by Benoît PECCATTE over 4 years ago

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

Updated by Benoît PECCATTE over 4 years ago

  • Target version changed from 3.2.0~rc2 to 3.2.0
#14

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.2.0 to 3.2.1
#15

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.2.1 to 3.2.2
#16

Updated by Alexis MOUSSET about 4 years ago

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

Updated by Janos Mattyasovszky about 4 years ago

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

Updated by François ARMAND almost 4 years ago

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

Updated by François ARMAND over 3 years ago

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

Updated by Vincent MEMBRÉ over 3 years ago

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

Updated by Vincent MEMBRÉ over 3 years ago

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

Updated by Vincent MEMBRÉ over 3 years ago

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

Updated by François ARMAND over 3 years ago

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

Updated by François ARMAND about 3 years ago

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

Updated by François ARMAND about 3 years ago

#26

Updated by Alexis MOUSSET almost 3 years ago

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

Updated by Vincent MEMBRÉ almost 3 years ago

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

Updated by Vincent MEMBRÉ almost 3 years ago

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

Updated by Vincent MEMBRÉ over 2 years ago

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

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.2.0~rc2 to 4.2.0
#31

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.2.0 to 4.2.1
#32

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.2.1 to 4.2.2
#33

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.2.2 to 4.2.3
#34

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.2.3 to 4.2.4
#35

Updated by François ARMAND over 2 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 :)

#36

Updated by François ARMAND over 2 years ago

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

Updated by François ARMAND over 2 years ago

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

Also available in: Atom PDF