Email confirmation url data
Hey all,
Is there a way for the email confirmation url (at signup) to pass the access_token, and other informations differently than within the url hash?
By default it seems these informations are added in the hash of the url provided in the supabase auth settings:
https://my_URL/#access_token=XXXX&expires_in=3600&refresh_token=XXXX&token_type=bearer&type=signup
The problem is that I'm using supabase in the backend only (building a client with no JS) and I'd like the link to call and provide access_token etc. to the backend which can then redirect the user to the correct page with the appropriate cookies. But sadly the hash does not exists on the backend side it's just ignored.
Thanks in advance
Is there a way for the email confirmation url (at signup) to pass the access_token, and other informations differently than within the url hash?
By default it seems these informations are added in the hash of the url provided in the supabase auth settings:
https://my_URL/#access_token=XXXX&expires_in=3600&refresh_token=XXXX&token_type=bearer&type=signup
The problem is that I'm using supabase in the backend only (building a client with no JS) and I'd like the link to call and provide access_token etc. to the backend which can then redirect the user to the correct page with the appropriate cookies. But sadly the hash does not exists on the backend side it's just ignored.
Thanks in advance
