Hi, I am trying to integrate Supertokens with echo-labstack. I followed this example https://github.com/supertokens/supertokens-golang/blob/master/examples/with-labstack-echo/main.go. Echo advocates to return errors from your Handlers, which will then be handled by their HTTP Error Handler (which you can customize). This works fine until I introduce the session.VerifySession in my middleware, as per the example (wrap it to turn it into a echo.MiddlewareFunc). As soon as I use this middleware on my routes, they always return

200

(empty body), no matter how may errors I return from my handlers. As soon as I remove the session.VerifySession echo'fied middleware, I get the actual errors. It seems as if the session.VerifySession middleware is swallowing the echo error and just returning a

200

instead. Anybody any idea what could be causing this?

Hello, I am facing blocking issue. I need to use the

exposeAccessTokenToFrontendInCookieBasedAuth: true

to verify a socket connection (as per https://supertokens.com/docs/session/common-customizations/sessions/with-websocket) I get an error that this option is not valid. I guessed it was because I was not using the latest version of the lib

supertokens-node

. Indeed I was using the

13.1.5

. Now that I updated to the

14

, it's working. But now I get an error

The running SuperTokens core version is not compatible with this NodeJS SDK

. I am using the

managed core

and I guess that the core was instantiated with a previous version. As I have no control on the core, how can I solve this?

Hi, I'm getting a 401 : Unauthorized message while calling the refresh and sign out api's. Here are the cookies being set in the request.

Hi, i try to use supertokens on nuxtjs with nuxt-auth. i have write a custom scheme extends cookies scheme. The question is, can i use "sIRTFrontend" to determine whether the session is alive on the middleware checking?

I have an issue with refreshing tokens with Next'js & Nest.js. I have followed guide for Sessions with Server Components: https://supertokens.com/docs/thirdparty/nextjs/app-directory/protecting-route#sessions-with-server-components--pre Everything works fine until the access token expires and new one has to be issued. Then at this moment I receive an error that prevents anything from rendering.

Warning: Functions are not valid as a React child

Refreshing the page afterwards with a valid access token doesn't cause issue. This stacktrace also mentions

SessionAuth

component, which makes me suspect that it's problem with the SuperTokens itself. Let me write this step by step what happens: 1. Refresh token epxires. 2. Browser sends two requests to:

/auth/session/refresh

and then

/auth/session/verify

(but not always). Response status codes are

200

3. While these requests happen, nothing is being rendered. These requests set the cookies accordingly. Error pasted below. 4. Refreshing site once again makes everyghing "just appear" and application behaves as desired. I have tried lowering the time

ACCESS_TOKEN_VALIDITY

environment variable to a few seconds to make sure that it's the invalid access token that causes trouble.

Hi, I am stuggling to find how to refresh the session using the header transfer method , by manually doing XHR Requests to the /auth/ endpoints. It seems the that refreshed token is sent using cookies instead of response headers. Currently I am trying with the following POST: What am I doing wrong?

api.post('/auth/session/refresh', 
           null,
           {
             headers: {
               Rid: "session",
               Authorization: "Bearer "+ refreshToken,
               "St-Auth-mode": "header", 
            }
          });

Hi, Anyone know why when I implement the

getUserById

in

nestjs

, it return me

shell
[Nest] 1229  - 18/02/2023, 3:49:21 pm   ERROR [ExceptionsHandler] Initialisation not done. Did you forget to call the SuperTokens.init function?
Error: Initialisation not done. Did you forget to call the SuperTokens.init function?
    at Function.getInstanceOrThrowError (/Users/xxx/Desktop/projects/chatgpt-studywithme/chatgpt-studywithme/backend/node_modules/supertokens-node/lib/build/recipe/thirdpartyemailpassword/recipe.js:229:15)
    at Function.getUserById (/Users/bytedance/Desktop/projects/chatgpt-studywithme/chatgpt-studywithme/backend/node_modules/supertokens-node/lib/build/recipe/thirdpartyemailpassword/index.js:82:33)
    at UserController.getUserInfo (/Users/xxx/Desktop/projects/chatgpt-studywithme/chatgpt-studywithme/backend/src/user/user.controller.ts:15:52)

my code is like:

ts
@Controller('user')
export class UserController {
  @Get()
  @UseGuards(new AuthGuard()) // For more information about this guard please read our NestJS guide.
  async getUserInfo(@Session() session: SessionContainer): Promise<User> {
    const userId = session.getUserId();
    // You can learn more about the `User` object over here https://github.com/supertokens/core-driver-interface/wiki
    const userInfo = await ThirdPartyEmailPassword.getUserById(userId);
    //....
    return userInfo;
  }
}

Hi guys, I changed my supertoken cookies (e.g. sFrontToken) to see how supertokens deals with it :-). I get now a  "Failed to execute 'atob' on 'Window'" exception, which is fine as the token is for sure corrupt. How can I programmatically resolve this situation? Calling e.g. Session.signOut() isn't callable as it will also throw the "Failed to execute 'atob' on 'Window'" exception. Any clue? Maybe I miss some callable function within the frontend which can force the deletion of all supertoken cookies. Thanks!

Hi, I'm trying to implement supertokens into my nestjs + nextjs application with ThirdPartyEmailPassword. I encountered an error when trying to signin/signup with Google. The account is successfully signup/signin in the development environment but the /signinup api failed with status code 500 on frontend 400 on backend, then the error got displayed on the form. When reload the frontend application, it does recognize that I've logged in and redirect to the home page tho.

@rp_st Hey guys, Do you have an SDK for Remix?