feat(agent-server): capture inbound auth credentials - #162
Merged
Conversation
xgtcode
force-pushed
the
feat/agent-server-inbound-auth
branch
from
August 6, 2026 14:46
46d9673 to
8114724
Compare
warm-wm
approved these changes
Aug 6, 2026
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
2 participants
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.
Add opt-in inbound auth capture for Agent Server.
When enable_auth is set, AgentServer now captures inbound Authorization and
X-Ve-TIP-Token headers, converts them into ADK-compatible credentials, and stores
them by app/user credential key for /invoke, /run_sse, and A2A requests.
This also adds an AgentKit credential service with direct write support, shared
framework-neutral inbound auth helpers, telemetry redaction for TIP tokens, and
coverage for identity-aware request handling so credentials are stored under the
effective verified user.
Validation: