Expose OAuth token management parameters across all providers #2222
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.
Closes #2208
All OAuth providers and the OIDC proxy now expose the three production-critical parameters for persistent token management across server restarts:
jwt_signing_key: Secret for signing FastMCP JWT tokenstoken_encryption_key: Secret for encrypting upstream OAuth tokens at restclient_storage: AsyncKeyValue storage for persisting client registrationsWhat Changed
OIDCProxy now accepts and passes through both encryption parameters to OAuthProxy.
All provider classes now expose all three parameters:
Production Usage
All three parameters work together to ensure tokens and registrations survive restarts in distributed deployments.
Documentation
Added "Production Configuration" sections (with version badges) to all provider integration guides demonstrating complete setup with Redis and environment variables.