Add OIDC authentication support to ToolHive management API server #634
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
This PR adds OIDC authentication support to the ToolHive management API server by reusing the existing authentication middleware from the
pkg/authpackage.Changes
thv servecommand:--oidc-issuer,--oidc-audience,--oidc-jwks-url,--oidc-client-idthv runandthv proxycommandsArchitecture
The implementation follows the same pattern used in other ToolHive commands:
auth.JWTValidatorConfigto configure JWT validation with OIDC discovery supportauth.GetAuthenticationMiddleware()automatically chooses between:Benefits
Testing
thv serve --helpUsage Examples
This addresses the need for enterprise-ready authorization in the management API server while maintaining consistency with the existing security architecture.