patch: API key to localai service calls #421
Merged
Conversation
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
frontend/src/components/EmbeddingSelection/LocalAiOptions/index.jsxConsider storing the API key in a secure place like cookies with httpOnly flag set to true or in the server-side session. This way, the key will not be accessible through JavaScript and will be automatically sent with each request to the server. // Example of storing API key in a secure cookie
document.cookie = "apiKey=" + apiKeyValue + "; Secure; HttpOnly"; |
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.
connect #417
Passthrough API key for all LocalAI API calls when defined by the user either in embedder or LLM setup