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
{{ message }}
This repository has been archived by the owner on May 10, 2024. It is now read-only.
When requesting a token (with an login endpoint) I would like to limit created token to operate only on selected collections and perform only limited actions.
Reason: There may be a USER who is a SYSTEM/CLUSTER-level user that is owning multiple collections for multiple applications in his/her cluster. A Backup Maker Operator could assign credentials dynamically during backup execution, and every ScheduledBackup can get its own scoped JWT that would allow to upload only to its own collection
In short words with this pattern we could allow to create a better isolation on application level in same user account.
The text was updated successfully, but these errors were encountered:
When requesting a token (with an login endpoint) I would like to limit created token to operate only on selected collections and perform only limited actions.
Reason: There may be a USER who is a SYSTEM/CLUSTER-level user that is owning multiple collections for multiple applications in his/her cluster. A Backup Maker Operator could assign credentials dynamically during backup execution, and every ScheduledBackup can get its own scoped JWT that would allow to upload only to its own collection
In short words with this pattern we could allow to create a better isolation on application level in same user account.
The text was updated successfully, but these errors were encountered: