Overview

This epic implements the upstream_inject outgoing auth strategy for vMCP (RFC-0054). The strategy reads upstream IDP access tokens from identity.UpstreamTokens (a map[string]string populated by the embedded authorization server in Mode B) and injects them as Authorization: Bearer headers on outgoing backend requests. It also extends token_exchange with an optional SubjectProviderName field for RFC 8693 subject resolution from upstream provider tokens.

Background

RFC-0052 extended the auth middleware to populate identity.UpstreamTokens after TH-JWT validation, and RFC-0053 wired the embedded AS into vMCP. However, no outgoing auth strategy currently consumes those upstream tokens — backends requiring upstream provider credentials (e.g., a GitHub MCP server needing a GitHub access token) cannot receive them. This epic completes the pipeline by adding the upstream_inject strategy and the startup validation rules V-01, V-02, and V-06 that guard against misconfiguration.

Task Breakdown

Acceptance Criteria

• upstream_inject strategy reads identity.UpstreamTokens[providerName] and injects Authorization: Bearer on outgoing backend requests
• ErrUpstreamTokenNotFound sentinel is defined and returned (wrapped with %w) when the provider's token is absent
• TokenExchangeStrategy uses the upstream provider token as subject when SubjectProviderName is set
• Startup validation V-01 (no AS present), V-02 (provider not in AS upstream list), and V-06 (empty providerName) fail fast with descriptive errors
• Kubernetes CRD supports type: upstreamInject with UpstreamInjectSpec.providerName
• CRD TokenExchangeConfig supports subjectProviderName field
• UpstreamInjectConverter converts CRD resources to BackendAuthStrategy
• All new types have SPDX headers, kubebuilder markers, and deepcopy regenerated
• All linked task issues completed

References

• RFC-0054: https://github.com/stacklok/toolhive-rfcs/blob/main/rfcs/THV-0054-vmcp-upstream-inject-strategy.md
• RFC-0052 (multi-upstream IDP support): Auth Server: multi-upstream provider support #3924
• RFC-0053 (embedded AS in vMCP): vMCP: add embedded authorization server #4120