Repository navigation
docs: clarify token privilege scoping - #1357
Conversation
Add a Privilege Scoping section to tokens.md answering #378: API tokens are identity-scoped — they carry the exact privileges, roles, and permissions of the user account within the organization and environment selected by the request context. Layer5 Cloud does not currently support fine-grained, token-specific privilege scopes. Content from #1101 by Aamod007, landed via this branch because that PR's merge with master could not be pushed back to the fork (the OAuth token used lacks the workflow scope the merge commit's workflow-file deletions require). Signed-off-by: Marcus <158522975+marblom007@users.noreply.github.com>
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 30 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
🚀 Preview deployment: https://docs.layer5.io/pr-preview/pr-1357/
|
Lands the docs change from #1101 (by @Aamodx6, who is the commit author here) as a clean tokens.md-only branch.
Why a replacement PR
#1101 also carried changes to two PR-preview workflow files that
masterhas since deleted/replaced (build-docs-preview.yml/deploy-docs-preview.yml), which conflicted and caused its failing preview check. Dropping those files via a merge commit on the fork branch turned out not to be pushable: the merge commit deletes workflow files, and GitHub refuses workflow-file changes from an OAuth token without theworkflowscope. This branch carries the identical docs change — the diff istokens.md, +6 lines — so the contribution can land now.Change
Adds a Privilege Scoping section to
content/en/cloud/concepts/identity-and-security/tokens.md, answering #378: API tokens are identity-scoped, carrying the user's exact privileges within the organization/environment selected by the request context, and Layer5 Cloud does not currently offer fine-grained token-specific scopes.#1101 will be closed as superseded by this PR once this merges.