Merged
Conversation
RafaelPo
force-pushed
the
accept-jwt-for-authentication
branch
from
1892b44 to
1ff2771
Compare
Allows configuring additional allowed Host headers via a comma-separated env var, enabling cross-Docker-network access (e.g. host.docker.internal). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
RafaelPo
force-pushed
the
accept-jwt-for-authentication
branch
from
1ff2771 to
d906235
Compare
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
2 participants
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.
This allows Supabase JWTs to be passed through to the API. The thinking is that ER-CC would send the remote MCP server the users JWT, and the MCP server would pass that along to the API, just as it does when running locally.
It should be backwards compatible
Needs testing