influxdata / influxdata/docs-v2
Docs do not describe how user and token permissioning interact
@jstirnaman is already working on this.
Since Nov 4, 2021.
- Dominant language
- JavaScript
- Stars
- 82
- Forks
- 326
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
A token can be 'owned' by a user. The user gains all the permissions of all the tokens that they own, *including inactive tokens* - need to confirm this is the desired behaviour.
So there is no CLI command currently to directly update permissions for a user (although we can do fine-grained permissioning via the API with various `POST .../members` and `POST .../owners` requests).
*But*, a 'user' can be given more generic permissions by owning tokens. The admin user created by `influx setup` is admin exactly because they own an operator token.
This could cause confusing behaviour if users of the database assume that the admin user created by `influx setup` has administrator privileges separate from owning the operator token - it does not. Removing the operator token will severely limit the permissions of the (formerly) admin user.
##### Relevant URLs
Current docs that don't describe well how to give permissions to users: https://docs.influxdata.com/influxdb/v2.0/users/create-user/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.