Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Secure API keys with a backend proxy #3

Closed
mme opened this issue Nov 16, 2023 · 1 comment · Fixed by #14
Closed

Secure API keys with a backend proxy #3

mme opened this issue Nov 16, 2023 · 1 comment · Fixed by #14
Labels
enhancement New feature or request Next Release This should be implemented in the next release

Comments

@mme
Copy link
Owner

mme commented Nov 16, 2023 •
edited
Loading

Right now, the API key can be extracted from the frontend code. Create a proxy to secure the API key.

Frameworks:

  • express.js
  • next.js
  • remix
  • standalone

Support "freezing" instructions to prevent prompt based attacks. CORS to prevent embedding. Add rate-limiting.
@mme mme added the enhancement New feature or request label Nov 16, 2023
@mme mme mentioned this issue Nov 16, 2023
Open
@mme
Copy link
Owner Author

mme commented Nov 17, 2023

CORS should be implemented by the library user. Freezing will be supported in the assistant based API

mme added a commit that referenced this issue Nov 17, 2023
@mme
Move frameworks to dev dependencies #3
03b1b9f
@mme mme added the Next Release This should be implemented in the next release label Nov 20, 2023
@mme mme mentioned this issue Nov 22, 2023
Merged
@mme mme closed this as completed in #14 Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request Next Release This should be implemented in the next release
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add Beak.js server mme/beakjs
1 participant
@mme