Replies: 2 comments 1 reply
-
I don't use self hosting but do you have no spaces between the URLs and are they the full urls including http? |
Beta Was this translation helpful? Give feedback.
-
This really seems to be a bug. We try to access this from our Nuxt 3 Frontend with nuxt-supabase package, but is does not work. The redirectTo parameter seems always to be ignored, no matter what settings are done in supabase. It only accepts the SITE_URL, not any other which we send. Currently we try to find a workaround on our client side but this should be investigated. To reproduce just create a frontend (we use Nuxt 3 with nuxt-supabase package) and supabase instance (self host) and use "supabase.auth.resetPasswordForEmail()" with redirectTo parameter. We have the additional redirect URLS correctly as in the question here without spaces:
You can make redirectTo to a fixed string too, same result, it gets ignored by supabase and yes, our FRONTEND_DOMAIN has a valid value, we console.log it on localhost, it gets correctly parsed into redirectTo.
|
Beta Was this translation helpful? Give feedback.
-
I have a self hosted Supabase using docker, and the additional redirect URLs didn't trigger when this code ran
const { data, error } = await supabase.auth.resetPasswordForEmail(email.value, {
redirectTo:
${config.public.FRONTEND_DOMAIN}/recover
,});
it's always redirects to SITE_URL even the config.public.FRONTEND_DOMAIN contains one of the URLs I set in the ADDITIONAL_REDIRECT_URLS
here is how I set it
and here is the environment in docker compose
It's either a bug or something I missing.
Beta Was this translation helpful? Give feedback.
All reactions