Repository navigation
Access Keys: scripts and agents call the API with a user key (0.1.11) - #9
Merged
Merged
Conversation
The edge accepted only the browser session, so agents signed in headless with a person's credentials to file issues. Declare the tracker Access Key space (tracker:read, tracker:write) with bearerPassThrough, and accept the assertion: Project-bound, user subject only, acting as that user with the Viewer role. Assertions are never forwarded to Directory.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
Tracker's edge accepted only the browser session cookie.
apthtokens got a 302, the Project had notrackerAccess Key space, and agents filed issues by signing in headless with a person's credentials.What
catalog/entry.yaml:bearerPassThroughand anaccessKeysspace (audiencetracker, prefixtrk, scopestracker:read/tracker:write), the same shape asagent-guide.cmd/server/internal/api/keys.go(keyActor): an assertion must carry this Project, a user subject, andtracker:readforGETortracker:writeotherwise. The key acts as its user with the Viewer role; the Platform role is not looked up, so Admin-only routes stay with signed-in users.GET /peopleanswersunavailable, avatars answer 403key_subject.raw_key_not_accepted.design/API.md§ Access Keys (v0.1.11); OpenAPI error codes; release version 0.1.11.Review focus (authentication boundary)
appthrust.io/projectclaim is the tenant boundary. The avatar route authenticates outsideroute()and refuses keys separately.Verification
go vet ./cmd/...,go test ./cmd/...against a disposable Postgres 17 (TestAccessKeyActsAsItsUserWithinScopeAndProjectran, not skipped),bun test hack./me).