influxdata / influxdata/influxdb
Tokens and User Permissioning in InfluxDB OSS
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
This epic will track improvements in user experience around tokens and user permissions.
OSS has several differences with cloud, notably:
* users in OSS are added via the CLI instead of invited
* OSS already supports multi-org, Cloud does not yet
* OSS has a special "Operator" token that has all permissions on all orgs. Cloud does not have the "Operator" concept as it does not yet support multi-org. Both OSS and Cloud have "All-access" tokens that have all permissions in a single org.
* OSS already supports "member" vs "owner" permissions, Cloud does not yet
Contributor guide
Research direction
This is a broad epic covering tokens, user permissions, and differences between InfluxDB OSS and Cloud, but it names no files, tests, or entry points. Start by breaking the OSS CLI, Operator and All-access tokens, and member-versus-owner permissions into separately scoped tasks; completion criteria are not defined in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100