chore(auth): use FastAPI's HTTPBearer for JWT token extraction #240
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.
Applicable issues
Bearer: JWT#196Description of changes
This pull request improves authentication handling in the
FromRequestDeploymentMixinclass by integrating FastAPI'sHTTPBearerauthentication scheme. Key updates include:aidial_sdk/deployment/from_request_mixin.py: ImportedHTTPBearerfrom FastAPI to support bearer token authentication.aidial_sdk/deployment/from_request_mixin.py: Introduced a_bearerclass attribute initialized withHTTPBearer(auto_error=False)to enable optional error raising on missing/invalid tokens.aidial_sdk/deployment/from_request_mixin.py: Refactored thefrom_requestmethod to use_bearerfor token extraction. The method now processes theAuthorizationheader using_bearerand extracts the token from the resulting credentials.These changes address an issue where the JWT token was not correctly retrieved from the
Authorization: Bearerheader.Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.