On a self hosted Supabase: changing the email via generateLink() and using the returned action_link as described in the docs does only seem to work when both links are generated and clicked (current and new email) - GOTRUE_MAILER_SECURE_EMAIL_CHANGE_ENABLED does not seem to have any effect when enabled in docker-compose.yml also since it doesn't seem to have any implementation in the auth codebase? https://github.com/supabase/auth/blob/6ac56244bf885729b6ed8815dbed39dc296a927b/internal/api/verify.go#L524
Is this stale / deprecated? In a self-hosted environment, due to this I don't seem able to disable the need for double checking / clicking both links (old and new email).
Interestingly, in local dev environment it does indeed work (by setting double_confirm_changes = false in supabase/config.toml) so it seems it is only related to self-hosting?
On a self hosted Supabase: changing the email via
generateLink()
and using the returnedaction_link
as described in the docs does only seem to work when both links are generated and clicked (current and new email) -GOTRUE_MAILER_SECURE_EMAIL_CHANGE_ENABLED
does not seem to have any effect when enabled in docker-compose.yml also since it doesn't seem to have any implementation in theauth
codebase? https://github.com/supabase/auth/blob/6ac56244bf885729b6ed8815dbed39dc296a927b/internal/api/verify.go#L524Is this stale / deprecated? In a self-hosted environment, due to this I don't seem able to disable the need for double checking / clicking both links (old and new email).
Interestingly, in local dev environment it does indeed work (by setting
double_confirm_changes = false
insupabase/config.toml
) so it seems it is only related to self-hosting?