-
Notifications
You must be signed in to change notification settings - Fork 881
Implement scoping for RBAC - APIs merged with User Roles #722
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
Labels
api
Area: HTTP API
Comments
Hey team! Please add your planning poker estimate with ZenHub @Emyrk @f0ssel @johnstcn |
We are not doing workspace agent tokens so we do not need this issue right now. |
Workspace agent tokens have their own auth flow/tokens. RBAC is not handling the scoping. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is to allow tokens to restrict the scope of the permissions the user has. The token should always restrict the permission set to a subset of permissions. It should never allow privilege escalation.
Example: A devurl token would have
*.devurl.*.read
to only allow reading of devurls.Implementation notes
To prevent privilege escalation, just run
Authorize()
on both the user's permissions and the token'sThe text was updated successfully, but these errors were encountered: