Client and multiple logged in users

[axel-at-drom]

I've fought with this issue for a day now, reading and re-reading the docs and all of the several issues that seem to be related with it, and I'm still not sure what would be the best way to deal with multiple users in a fastapi app using supabase-py. The problem:
When I instantiate one client instance and call sign_in_with_password() consecutively with several different users, I don't seem to be able to, e.g., insert new rows in a table with RLS activated where users can only insert rows associated with their own user_id, except for the last logged in user. Somehow, the client seems to be bound to this last logged in user.

I have found several suggestions on how to get around this:

• client.auth.set_session but this seems to require sending the refresh token together with the auth token which means I need to store the refresh token in the client together with the auth token and send it along with every request. This seems wrong to me.
• Creating new clients for every user (or even on every api call) and calling create_client with the token in the options argument. But what about this: Supabase Client Requires Explicit sign_out() to Terminate Properly supabase-py#926. It seems to be best practice to shut down clients at some point by calling sign_out on them.

What is the official way to deal with this (extremely common, I imagine) problem?

[silentworks]

If you are using FastAPI then follow what FastAPI states about i/o bound operations and how to handle them using dependency injection. This isn't really a concern of the Supabase python documentation as it's a framework specific thing. You should use dependency injection when using FastAPI for your dependencies.

# create your async client
async def create_supabase() -> AsyncClient:
    return await acreate_client(supabase_url, supabase_key)

# use it inside a route handler
@app.get("/todos")
async def list_all(supabase: AsyncClient = Depends(create_supabase)):
    response = await supabase.table("todos").select().execute()
    return response.data

[axel-at-drom]

Thank you. The question was more like:
Should I create a new Client for each request, or should I create one per user, or should I try to set_session for each request?
I've decided on creating one Client per user and managing that in an extra class. That seems to be working alright.

[gpkc]

@silentworks Does that mean that supabase/supabase-py#926 isn't an issue anymore?

The way you've shown, you're not calling sign_out on every newly created client. Meaning, unless that's not an issue anymore, it's always potentially leaving resources behind.

It is still mentioned: https://github.com/supabase/supabase-py/blob/main/src/supabase/README.md?plain=1#L156-L162