Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Application(API) Keys Scoping #37

Open
himank opened this issue Mar 23, 2023 · 0 comments
Open

Application(API) Keys Scoping #37

himank opened this issue Mar 23, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@himank
Copy link

himank commented Mar 23, 2023

In Tigris(or probably in other cloud platforms as well), an account is mapped to a user. This user can have multiple projects in his account. Each project can have Api keys that the user will use to interact with the platform. This means a single API key won't work for a user. API keys need to be scoped to a user and then to a project.

The ask here is whether a scoping can be introduced when generating API keys. Then that scoping actually can be anything. For example, in the future, for example, we can scope our keys like user-->project-->environment

@akajla09 akajla09 added enhancement New feature or request server labels Mar 23, 2023
@akajla09 akajla09 removed the server label Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants