Repository navigation
feat(mcp): support workload JWT assertion authentication - #304
Merged
Merged
Conversation
danielkov
marked this pull request as ready for review
October 23, 2026 19:50
danielkov
changed the title
![kit-code-agent[bot]](https://avatars.githubusercontent.com/in/4797102?s=60&v=4){kind=small}
danielkov
enabled auto-merge (squash)
October 23, 2026 21:05
danielkov
disabled auto-merge
October 23, 2026 21:47
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.
Summary
Add generic RFC 7523 workload JWT assertion authentication for MCP servers. This change does not add workload authentication for inference.
Configure
auth.type: workload_identitywithtokenFile,expectedIssuer,tokenEndpoint, andresourcein the existing MCP configuration. Kit validates HTTPS issuer metadata, reopens the assertion file on exchange, and caches resource-scoped access tokens until shortly before expiry. Acquisition is bounded and serialized, with no browser or saved-credential fallback.The issuer must explicitly permit repeated use of an unchanged assertion when the deployment needs it. Process-memory restores require restarting Kit and resuming its transcript.