Fixes missing Bearer in token auth #279
Merged
Conversation
This file contains 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
Open ai now requires the authorization header to contain the Bearer scheme. This was resulting in errors like the below: src-server-1 | Caused by: io.ktor.client.plugins.ClientRequestException: Client request(POST https://api.openai.com/v1/embeddings) invalid: 401 Unauthorized. Text: "{ src-server-1 | "error": { src-server-1 | "message": "You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.", src-server-1 | "type": "invalid_request_error", src-server-1 | "param": null, src-server-1 | "code": null src-server-1 | } src-server-1 | } src-server-1 | " This can be corrected by setting the headers in the openai client to `mapof("Authorization" to Bearer <token>")`.
anamariamv
requested review from
a team,
javipacheco and
victorcrrd
and removed request for
a team
raulraja
approved these changes
Jul 27, 2023
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.
Open ai now requires the authorization header to contain the Bearer scheme. This was resulting in errors like the below:
src-server-1 | Caused by: io.ktor.client.plugins.ClientRequestException: Client request(POST https://api.openai.com/v1/embeddings) invalid: 401 Unauthorized. Text: "{
src-server-1 | "error": {
src-server-1 | "message": "You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.",
src-server-1 | "type": "invalid_request_error",
src-server-1 | "param": null,
src-server-1 | "code": null
src-server-1 | }
src-server-1 | }
src-server-1 | "
This can be corrected by setting the headers in the openai client to
mapof("Authorization" to Bearer <token>").