Feat: Add Supabase auth headers to api CORS policy#824
Merged
ben-fornefeld merged 1 commit intoJun 24, 2025
Merged
Conversation
dobrac
approved these changes
Jun 24, 2025
dobrac
approved these changes
Jun 24, 2025
Member
Author
i might specify - from browser with access to the supabase auth tokens of a user on the same cluster. api keys worked already inside browser environments before this addition |
ValentaTomas
pushed a commit
that referenced
this pull request
May 4, 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
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.
In order to enable usage of the
e2bSDK inside a browser environment + authorizing to the api via the user'sSupabase Token, this PR updates the CORSAllowHeaderspolicy for theAPIaccordingly .These additions were tested on my local cluster while developing this dashboard feature.