fix: update encryption key retrieval to use only USER_API_KEYS_ENCRYPTION_SECRET#137
Merged
Merged
Conversation
…TION_SECRET; remove supabase secret key fallback
This was referenced May 15, 2026
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.
Summary
Require
USER_API_KEYS_ENCRYPTION_SECRETfor stored user API key encryption.Changes
API_KEYS_ENCRYPTION_SECRET.SUPABASE_SECRET_KEY.USER_API_KEYS_ENCRYPTION_SECRET.Why
Stored user API keys should be encrypted with a dedicated secret only. Falling back to the Supabase service role key couples unrelated secrets and makes rotation/deployment behavior harder to reason about.
Testing
npm run build --prefix backendpasses in the private repo.open-source-export/backend:@types/cors,@types/express,@types/multer.