feat(cloud): add OAuth2/JWT authentication support for CloudStrategy#20
Merged
innsd merged 1 commit intovolcengine:mainfrom Dec 12, 2025
Merged
feat(cloud): add OAuth2/JWT authentication support for CloudStrategy#20innsd merged 1 commit intovolcengine:mainfrom
innsd merged 1 commit intovolcengine:mainfrom
Conversation
Introduces support for 'custom_jwt' authentication type alongside existing API key authentication. Updates config, strategy, and runner logic to handle JWT/OAuth2, including new fields for OIDC discovery URL and allowed clients.
Contributor
Author
|
@cuericlee @yaozheng-fang could you please help approve it |
innsd
approved these changes
Dec 12, 2025
innsd
approved these changes
Dec 12, 2025
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 support for OAuth2/JWT (Custom JWT Authorizer) authentication mode in CloudStrategy and HybridStrategy, allowing Runtime to validate requests using OIDC-based JWT tokens instead of API Key.
Changes:
Add AUTH_TYPE_KEY_AUTH and AUTH_TYPE_CUSTOM_JWT constants
Add runtime_auth_type, runtime_jwt_discovery_url, and runtime_jwt_allowed_clients configuration fields to:
CloudStrategyConfig
HybridStrategyConfig
VeAgentkitRunnerConfig
Implement _build_authorizer_config_for_create() and _build_authorizer_config_for_update() helper methods to construct appropriate AuthorizerConfiguration based on auth type
Update _create_new_runtime() and _update_existing_runtime() to use new authorizer config builders
Update status() and invoke() methods to handle JWT auth scenarios:
Skip API key retrieval for JWT auth
Skip ping check in status() for JWT auth (no token available)
Require Authorization header in invoke() for JWT auth