Did Supabase Change Auth Hooks?
I have been using auth hooks for a while now based on the supabase documentation.
https://supabase.com/docs/guides/auth/auth-hooks/custom-access-token-hook
All of a sudden, users logging into our application were getting errors related to the "custom_access_token_hook" despite no changes to either our codebase or supabase configuration.
Moving the Auth Hook / Function to a different schema seems to have fixed the problem, but I'd like to work out why?
Has anyone else had issues?
Custom Access Token Hook | Supabase Docs
Customize the access token issued by Supabase Auth
6 Replies
The auth hook is schema bound. I remember having this issue when I moved it from
public
to a private one.
You probably can change it from here. I found something similar in the dashboard.Key thing is, it has been being used and working in the schema is was in for weeks, and then it suddendly stopped.
Without knowing the errors it is hard to say.
Not heard of any changes.
What schema was it in?
app_auth, which appears to have been created only for this
Well I'll assume it was created by you or your AI if you use one as it is not a standard schema.
Looking here I don't see in changes that seem relevant to the hook.
https://github.com/supabase/auth/pulls?q=is%3Apr+token+is%3Aclosed+
Very weird