You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: