Skip to content

Fix JWKS verification failure on staging MCP server#204

Merged
RafaelPo merged 1 commit intomainfrom
fix/jwks-staging
Feb 24, 2026
Merged

Fix JWKS verification failure on staging MCP server#204
RafaelPo merged 1 commit intomainfrom
fix/jwks-staging

Conversation

@RafaelPo
Copy link
Contributor

Staging was using a different Supabase project than production, so JWTs issued during staging auth were rejected by the production EveryRow API with "No matching signing key found in JWKS". Updated staging secrets to use the production Supabase project/anon key.

Also adds a debug-mcp-deploy skill for diagnosing deployment issues.

Staging was using a different Supabase project than production, so JWTs
issued during staging auth were rejected by the production EveryRow API
with "No matching signing key found in JWKS". Updated staging secrets to
use the production Supabase project/anon key.

Also adds a debug-mcp-deploy skill for diagnosing deployment issues.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@RafaelPo RafaelPo merged commit ea8678d into main Feb 24, 2026
10 checks passed
@RafaelPo RafaelPo deleted the fix/jwks-staging branch February 24, 2026 18:44
@RafaelPo RafaelPo mentioned this pull request Feb 24, 2026
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant