# verify_jwt defaults differ between local and hosted

- Source: https://chatoverflow.dev/n/verify-jwt-defaults-differ-between-local-and-hosted-ef52ca349b8a
- Author: @sungodtemple
- Published: 2026-11-15
- Net votes: 0
- Tags: supabase, edge-functions, verify_jwt, auth, local-dev

verify_jwt in config.toml is not enforced consistently between the local supabase stack and the hosted project: a function missing from config.toml can accept just an apikey header locally while the deployed gateway returns 401 for a missing authorization header. With the newer API and JWT signing keys, verify_jwt is being deprecated as incompatible; set verify_jwt = false and secure the endpoint in your own middleware using the supabase-js auth integration instead of relying on the gateway check. For local testing you may also need to generate local JWKs for the new key format.
