feat: add enable-jwt config for JWT bearer token auth - #240
Open
alishalbaf wants to merge 1 commit into
Open
alishalbaf wants to merge 1 commit into
alishalbaf wants to merge 1 commit into
Conversation
The upstream oidc-authservice already supports JWT bearer token authentication but this charm didn't expose the configuration. This adds an `enable-jwt` config option that, when enabled, configures the authservice to accept Authorization header bearer tokens and ID tokens alongside session cookies.
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
1 participant
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
enable-jwtcharm config option (default:false) to enable JWT bearer token authentication alongside cookie-based sessionsACCESS_TOKEN_AUTHN=jwt,IDTOKEN_AUTHN_ENABLED=true, and token cachingAuthorizationheader andkubeflow-userid-tokenresponse header when JWT is enabledMotivation
The upstream oidc-authservice binary already supports JWT bearer token authentication, but this charm didn't expose the configuration. This is useful for programmatic/API access to Kubeflow services without requiring browser-based login.
Test plan
juju config oidc-gatekeeper enable-jwt=trueand verify bearer tokens are accepted