oh ok so, the

supabase

library is tagged to a commit which doesn't have

match

released. We can update that and publish a new release. As for the

dataclasses

bug let me think about it for a moment and get back to you

So sorry that you had to go through this

That would be great if you have the time. Thanks much!

fuzzy search query

I think 30% should be fine. I'm running a vanilla instance of Supabase with just the

countries

table and it seems to use about ~30% as well. Not too sure how to check exact breakdown though.

how do you configure what data associated with the user from the db is returned i the user_metadata object when a session is returned after loggin in?

Sure thanks

Hi, I have a question which I cannot find an answer for. Does supabase has a feature which would allow me to execute code when it detects that user have disconnected from realtime feed?

if i take that access_token returned by clicking on the magic link in an email (that's the only auth method i have set up right now) and pass that back as a header in a call to my server side api if I call client.auth.setAuth(access_token) it should work right? right now it's just returning null for me

these examples are wrong https://supabase.com/docs/reference/javascript/auth-setauth setAuth doesn't return an object that contains { error }

setAuth returns something like this {"access_token":"ey.......rNjfA","token_type":"bearer","user":null}

.setAuth()

is a pretty low-level thing. If you can, use

.signIn({refresh_token: ...})

- that will setup the session, current user, and background token refresh (at least in browser it should)

i switched to something more like this

supabase.auth.setAuth(headers.authorization);
    const { user } = await supabase.auth.api.getUser(headers.authorization);

@User when will the change be pushed?

the access_token is only useful for one hour. You should've gotten a refresh_token in the email login link, that's the one you want to use (with

signIn

)

well i changed it to be good for a week

Hey Maverick, Apologies for the delay. I'd say it'll take about another 30 mins or so at least

once that expires you can make a call with the refresh token to get a new access token so long as your refresh token hasn't been revoked

right?

that's... not optimal for security, 1h is already pretty long

you're probably right

yes, and if you use

signIn()

then the supabase lib should refresh tokens in the background

yea 30 mins works thanks for the help

i should only be sending the refresh token back server side once the access_token has expired

i have svelte kit rest api between my front end and supabase

Hi, is it possible to use a custom domain for the api endpoint on the cloud offering, instead of *.supabase.co?

when i try to sign in using my refresh token it just says invalid refresh token.... i set the jwt expiration down to 2 minutes in hopes that this would allow me to really test JWT expiry and replacing with a session using the refresh_token

refresh_token is single use, so make sure you're using the last one

right

why does the client keep making this call? https://otdbbakdeabkncevqxxh.supabase.co/auth/v1/token?grant_type=refresh_token