Β© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabaseβ€’7mo agoβ€’
13 replies
nameless

JWT Signing Keys

Im trying to migrate completely to the new JWT keys. Im using getClaims() in routes and middleware to check user auth. Even so when a user executes signOut(), getClaims() returns the user in claims.sub. How can i clear the claims after signOut()? Should i use it at this state? After some hours i also get this error:

Error [AuthApiError]: Invalid Refresh Token: Refresh Token Not Found
at handleError (../../../src/lib/fetch.ts:102:8)
at async _handleRequest (../../../src/lib/fetch.ts:195:4)
at async _request (../../../src/lib/fetch.ts:157:15)
at async (../../src/GoTrueClient.ts:2112:17)
at async (../../../src/lib/helpers.ts:228:25) {
__isAuthError: true,
status: 400,
code: 'refresh_token_not_found'
}
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

supabase new jwt signing keys
SupabaseSSupabase / help-and-questions
7mo ago
JWT Signing Keys in Swift?
SupabaseSSupabase / help-and-questions
7mo ago
Generating JWT with new Signing Keys
SupabaseSSupabase / help-and-questions
5mo ago
Python API: Migrating to JWT Signing Keys
SupabaseSSupabase / help-and-questions
6mo ago