User story #5627
closedReadonly API or otherwise restrictable API Accounts
Description
Hi,
currently it is possible to create different API Accounts for different tasks.
For outside interaction (other applications pulling data from rudder) the API works but not in all cases the accessing application should be permitted to do any changes in rudder.
Some way for this would be having accounts that are restricted to i.e. readonly accesses.
Updated by François ARMAND about 10 years ago
Hello,
A clearly valid use case !
Some more thought on it:
- do you want more than just read/write authorization granularity ? For example, we may thing that some coniguration details are not at all public (port, passwords - even only hashes, etc)
- as a first workaround, one can configure Rudder Apache to only accept GET method on API url. As we really use verbs semantic, GET === read-only (write is done with PUT or POST).
Updated by Benoît PECCATTE over 9 years ago
- Category set to API
- Target version set to Ideas (not version specific)
Updated by François ARMAND over 8 years ago
- Related to User story #5798: Different access levels for API keys / REST API authorizations and rights added
Updated by François ARMAND about 7 years ago
- Target version changed from Ideas (not version specific) to 4.3.0~beta1
Updated by François ARMAND about 7 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND about 7 years ago
Work in progess here: https://github.com/fanf/rudder/commit/601856f3a8879a9d073b1acc0f30e2bdfaf0f3e8
Updated by François ARMAND about 7 years ago
Work in progess here: https://github.com/fanf/rudder/commit/8dd3e90436d2bbf4149e11960d63bbf68e9cf4e8
Updated by François ARMAND about 7 years ago
Work in progess here: https://github.com/fanf/rudder/commit/798ab413c2d479a3238035b6f5dbbde4ef3e33f4
Updated by François ARMAND about 7 years ago
Work in progess here: https://github.com/fanf/rudder/commit/8151b7647c51ce28e01046770a2804b0b65ebf62
Updated by François ARMAND almost 7 years ago
Work in progess here: https://github.com/fanf/rudder/commit/2b73fc8c357aea732d4ba9fbc80e8b7469562162
Updated by François ARMAND almost 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1822
Updated by Rudder Quality Assistant almost 7 years ago
- Assignee changed from Vincent MEMBRÉ to François ARMAND
Updated by François ARMAND almost 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|808526a57b71934c8205fc2d6fa2f2003de6a72d.
Updated by Vincent MEMBRÉ almost 7 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.0~beta1 which was released today.
- 4.3.0~beta1: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by François ARMAND almost 7 years ago
- Related to deleted (User story #5798: Different access levels for API keys / REST API authorizations and rights)
Updated by François ARMAND almost 7 years ago
- Has duplicate User story #5798: Different access levels for API keys / REST API authorizations and rights added
Updated by François ARMAND almost 7 years ago
- Related to User story #7893: [API] Expose all configuration options from the WebUI in the API added
Updated by François ARMAND over 6 years ago
- Related to User story #13009: Documentation for API authorizations plugin added