chore: add custom-jwt-validation example

[kallebysantos]

Same as supabase/edge-runtime#642

Description

What kind of change does this PR introduce?

docs update

What is the new behaviour?

Since jwt verification will be deprecated, users should use --no-verify-jwt and do verification by their selves.

This PR adds some templates for jwt token verification.

Additional context

• related with https://github.com/orgs/supabase/discussions/34988
• partially solves Third Party Auth JWT not compatible with Edge Function edge-runtime#542

---

Note

Adds a custom JWT validation example with shared middleware for Supabase default auth and Clerk, plus setup docs.

• Examples:
  • Shared JWT templates in examples/edge-functions/supabase/functions/_shared/jwt/:
    • default.ts: verifies Supabase JWTs using JWT_SECRET with jose and exports AuthMiddleware.
    • clerk.ts: verifies Clerk-issued JWTs via remote JWKs (AUTH_THIRD_PARTY_CLERK_DOMAIN) and exports AuthMiddleware.
  • Edge function custom-jwt-validation/:
    • index.ts: demonstrates wrapping a handler with AuthMiddleware (default provider by default).
    • README.md: instructions for copying templates and required env vars.

^{Written by Cursor Bugbot for commit acd3949. This will update automatically on new commits. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
design-system	Ready	Preview	Comment	Nov 14, 2025 10:33am
docs	Ready	Preview	Comment	Nov 14, 2025 10:33am
studio-self-hosted	Error			Nov 14, 2025 10:33am
studio-staging	Error			Nov 14, 2025 10:33am
ui-library	Error			Nov 14, 2025 10:33am
zone-www-dot-com	Error			Nov 14, 2025 10:33am

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
studio	Ignored			Nov 14, 2025 10:33am

[vercel]

@kallebysantos is attempting to deploy a commit to the Supabase Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thanks for contributing to Supabase! ❤️ Our team will review your PR.

A few tips for a smoother review process:

• If you have a local version of the repo, run pnpm run format to make sure formatting checks pass.
• Once we've reviewed your PR, please don't trivially merge master (don't click Update branch if there are no merge conflicts to be fixed). This invalidates any pre-merge checks we've run.

[kallebysantos]

cc @laktek