fix(qdrant): send raw api key without Bearer prefix#1707
Open
ankit25bcs10610 wants to merge 1 commit into
Open
fix(qdrant): send raw api key without Bearer prefix#1707ankit25bcs10610 wants to merge 1 commit into
ankit25bcs10610 wants to merge 1 commit into
Conversation
Qdrant authenticates via the `api-key` header, which must contain the raw key. The header was built as `api-key: Bearer <key>`, so Qdrant rejected every request with 401/403. (The sibling `milvus` provider correctly uses `Authorization: Bearer <key>`.) Send the raw key in `api-key` and add a unit test for the header. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
The Qdrant provider builds its auth header as:
Qdrant authenticates via the
api-keyheader, which must contain the raw key — it does not use theBearerscheme. With theBearerprefix, Qdrant receivesapi-key: Bearer <key>and rejects every request with 401/403.For reference, the sibling
milvusprovider correctly usesAuthorization: Bearer <key>— the two schemes got crossed here.Fix
Send the raw key in the
api-keyheader, and add a unit test asserting the header shape.npm run format:checkpasses.