separate MCP ingress without basic auth to enable its own bearer auth#81
Open
vitek-rostislav wants to merge 5 commits into
Open
separate MCP ingress without basic auth to enable its own bearer auth#81vitek-rostislav wants to merge 5 commits into
vitek-rostislav wants to merge 5 commits into
Conversation
vitek-rostislav
force-pushed
the
rv/mcp-http-auth
branch
from
ae21bfe to
69d7081
Compare
grossmannmartin
requested changes
Jun 22, 2026
- to verify proper "http auth + mcp ingress + cloudflare" combination
grossmannmartin
approved these changes
Jun 23, 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
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.
Non-production domains (and any production domain in
FORCE_HTTP_AUTH_IN_PRODUCTION) are protected by nginx HTTP basic auth on the main ingress. Basic auth and the MCP Bearer token both use the singleAuthorizationheader, so while basic auth is enabled the Bearer token never reaches the application and external MCP clients (e.g. Claude Code) can't authenticate.This publishes the MCP paths through a second ingress without basic auth, so they stay reachable. These paths remain protected by the application itself (Bearer token on
/_mcp) or are public by the OAuth specification:/_mcpand/mcp/oauth(Prefix)/.well-known/oauth-authorization-serverand/.well-known/oauth-protected-resource(ImplementationSpecific, since ingress-nginx >= 1.12 rejects dots inExact/Prefixpaths by default)The MCP ingress reuses the certificate managed by the main ingress (same TLS secret,
cert-managerannotation dropped) to avoid issuing a duplicate certificate.