-
Notifications
You must be signed in to change notification settings - Fork 101
fix(api-keys): let members create MCP keys, and surface why creation failed #242
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 New permission tests fail because API-key callers are always treated as full admins
The new tests assert that a member's key keeps member-level access (
resolveKeyexpecting["org:member"]atapps/api/src/routes/v2/api-keys.http.test.ts:356-360), but every request authenticated with an API key is stamped with the top-level admin role (roles: apiKeyDefaultRolesatapps/api/src/services/ApiAuthorizationV2Layer.ts:120), so the member's key is treated as an administrator and these checks do not hold.Impact: The pull request does not pass its own newly added tests, so the change cannot merge cleanly and the member-vs-admin distinction it claims to test does not actually exist for key-authenticated callers.
Why the assertions can't hold at this revision
The member's credential is a standard key whose stored metadata pins
["org:member"], butApiAuthorizationV2Layerignores the resolved key'srolesand setstenant.rolestoapiKeyDefaultRoles(["root"]) for all API-key auth. Consequently:api-keys.http.test.ts:344-361creates an MCP key whose pinned roles come from[...tenant.roles](apps/api/src/routes/v2/api-keys.http.ts:130), i.e.["root"], so the resolved roles are["root"], not["org:member"].api-keys.http.test.ts:364-379expects a member to get a 403 creating a standard key, butrequireAdmin(["root"])succeeds, returning 200.api-keys.http.test.ts:381-406expects a 403 revoking a foreign key, butrequireAdmin(["root"])succeeds, returning 200.The role-propagation wiring that would make
tenant.rolesreflect the key's pinned roles lives in the CLI device-auth work that the PR description says is "not included and remains uncommitted locally," so the tests only pass in a working tree that has those uncommitted changes.Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.