influxdata / influxdata/influxdb
Permission related queries on Orgs, Data access and User access.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
### Discussed in https://github.com/influxdata/influxdb/discussions/23902
Originally posted by **vaishalisinghj** November 11, 2022
Hi All,
I am currently on the Influxdb v2 cloud.
use case :
When Creating **_Custom level Token_** , I have to check AllOrgs as my code needs permission to view Org list for an usecase.
But we now have an usecase wherein we have multiple Influx "comprising different companies, each needing to segregate data".
Question 1.
Does Checking AllOrgs mean Permission to view the org list does not mean permission to access the data in the org?
Question 2.
How can I see create a custom token allow access to Org List but not to data?
Question 3.
Can we Provide Also the Specific Org “user” that could potentially have more access than a standard user that is a single org ?
Question 4.
Can we give granular permission rather than checking the AllOrgs option directly?
If possible can you please share steps, and how can we perform them?
Thank you in advance
Contributor guide
Research direction
The issue is a set of unanswered questions about InfluxDB v2 Cloud custom-token permissions across organizations, including org-list visibility and granular access. No source files, tests, or entry points are mentioned; begin by reviewing the linked discussion and the current permission model. Done would require a decided scope and documented or implemented behavior for the requested access distinctions.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, cloud, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100