hey @User , @User can help with this. He will help out soon

if @User doesn't help by tomorrow, please could you open an issue about this in supertokens-python repo and we will definitely get back to you there by Monday.

Hey @User, any specific reason using gunicorn with an asgi based FastAPI application? Also, which version of supertokens-python are you using? For supertokens-python, version 0.3.0, you can set the parameter

telemetry=False

in init config and check if you are still getting the above error. If you are still encountering the same error, the library will need to be updated for the scenario where Fastapi is used along with an wsgi server. Currently we only support that for django

Hi @User , We are using Gunicorn as a process manager for our deployment to Google Cloud Run based on the documentation provided by FastAPI https://fastapi.tiangolo.com/deployment/server-workers/ & https://www.uvicorn.org/deployment/

Can you please provide a link for the supertokens-python, version 0.3.0, I cannot seem to find it in pypi. Do I have to use the dev-v0.3.0 available on Github?

We haven’t released 0.3.0 yet. Will probably do it today. Then you can find it in pypi

Sure, thanks.

@User , we will also be adding wsgi support for fastapi in this release.

That sounds great

Thanks a lot

Hi @rp @kakashi_44 thanks for the wsgi support in the new release. Our application is working successfully on the Google Cloun Run with telemetary=False in init function.

awesome!

Hi, what should we replace ``res`` with in ``await Session.createNewSession(res, userId);`` if we are using graphql.

hey @User , are you using us only for sessions? If not, then a new session is created automatically when the user signs in / up. If you are using us only for sessions, then you should create a separate end point for login / sign up which works independently to the grapqhl layer. Maybe there is a better way of doing this, I will have to investigate.

thanks, I researched a bit and figured it out. I have pasted the screenshot below

Sounds good. Just one case is if

getSession

throws a

TRY_REFRESH_TOKEN

error, then you need to send a 401 to the frontend. This can happen if a session exists, but the access token has expired. So your code should change to like:

try {
  const existingSession = await Session.getSession(...)
  ...
  return {
    id: data.id,
    ...
  }
} catch {
  if (err.type === Session.Error.TRY_REFRESH_TOKEN) {
    // return 401 to frontend
  } else {
    return InternalServerError(error);
  }
}

could you please explain the error to me

So the session works via an access and a refresh token. If the access token has expired, but the refresh token still exists, then

getSession

will throw this error. You should then send a 401 to the frontend which will then (via our SDK) try and call the refresh API automatically. Once a refresh is successful, the new access token is sent back to this API and this time,

getSession

should succeed.

Hello, I'm using FDI. I need to refresh token manually at SSR in nuxt (no idea how to do it another way) When i'm trying to refresh token manually (sending a

POST

to

/{apiBasePath}/session/refresh

) i'm always getting a 401... how should I do it corrctly? I'm sending all required params at query params, and it dont want to work

Hi @User , do you see any message along with the 401?

Also, sIdRefreshToken and sRefreshToken should be cookies not query params

no, only

401 unauthorized

A sample refresh API call looks like this:

curl 'https://localhost:3000/auth/session/refresh' \
  -X 'POST' \
  -H 'rid: session' \
  -H 'Cookie: sRefreshToken=ATa8vaSYm3PvteMeAnAuAE3a8tV0WlQDArCkhVmnkVIPthrHsdDpymIEssv%2BKXn5OSABMc%2Fw5zofn9Q%2BjKEs53rSf5A%2Bobxr7%2BBqTR9qOQO%2Bu8f7IozxMuY1KfwDiMKYOZRYjOW7BT5RE9E1kuOvcigqog5hNvyp1mYqF9VgO4Oho1mhX0s%2BjL5RV7ZdLN3RKqVrZQVm35Cy%2FqUvG7e7zhtMYX5AMSecA8OnZ7X%2By4VVnf7opkmy4L5UiWgmvUuVGZJ0OJwYRSCYpKyzYhso1LVFiTA6hXeStghiXaDMsNtgnXqktbk8JXnD4npOe3dVm3hlBZvOd0ol7beCoNvDaKFEgCEemZjBCL8BdsMtQ%2BYL2OOsiySBua57gumIhXIOp2AKb7tBIo15vqgB.02eddfb35c1e47b62defad9fd2a0517ece5b8e744df214916eb534cf289e0306.V2; sIdRefreshToken=0db5d679-7a7f-4d06-9cec-f3778aa0b2f7'

Also, are you trying to refresh the session in the backend?

or from the frontend?

I'm trying to do it at SSR, so its neither frontend or backend

at frontend refreshing works perfectly

So you want to do a refresh only from the frontend, and never from the web server

If you see that the access token has expired during SSR, you should send a "loading" screen to the frontend

which will manually refresh the session, and then reload the page