fix: pass effective jwt token to API calls#1088
Merged
Merged
Conversation
phact
approved these changes
Mar 10, 2026
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
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.
This pull request updates the authentication logic for API key users in the
src/dependencies.pyfile. The main change is that API key users now receive an effective JWT token, if available, when their user object is created. This improves compatibility with systems that require JWT tokens, such as OpenSearch OIDC.Authentication improvements:
session_managerdependency to theget_api_key_user_asyncfunction to enable retrieval of JWT tokens.session_manager.get_effective_jwt_token(None, None)and assigned it to thejwt_tokenfield of the user object, replacing the previous default ofNone. [1] [2]