Hey guys, which functions would i have to mock out (via jest) to write an integration test for a user signing in -> to unverified email. I use the SessionAuth component, so some pointers would be great. (This component seems to be the one handling the redirection, but unsure of which functions to mock out from super tokens to make the component believe i'm an unverified logged in user)

Hello, I cannot access the ST dashboard on my backend anymore (core):

Hey! I'm integrating supertoken on my go-fiber backend but I can't seem to install supertokens when I run go mod tidy. It always gets stuck at

go: downloading github.com/twilio/twilio-go v0.26.0
go: downloading github.com/golang/protobuf v1.3.2
go: downloading github.com/niemeyer/pretty v0.0.0-20200227124842-a10e7caefd8e

Hi, can I send SMS using API, to a phone number that is not saved in the SuperTokens user management database? Thanks

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've come across a pretty strange behavior. I'm using the SDK in a react native app. In order to maintain the session state i routinely check "SuperTokens.doesSessionExist()" and with that answer go forward with an authorized/unauthorized user. What i have discovered is that when the session expires, the method "doesSessionExist", still resolves true.

Hello, I've implemented emailpassword recipe with fastify node.js backend and vue 3 frontend. I did the rest api endpoints authentication using verifySession as per the documentation. But whenever the access token expires it doesnt get refreshed through refresh token and im getting an error message: "try refresh token". I dont understand where im going wrong.

Hi, I'm thinking about switching my server environment to functions / edge functions. There's seemingly support for functions but your docs state:

Please refer the Serverless Deployment section (Towards the bottom of the navigation index)

Which I can't find, does it exist or am I blind? 😅 Regarding edge functions environment, I'd like to use Cloudflare Workers, do you offer native support for the runtime?

Hey guys, I want to use krakend.io API Gateway to enforce request level authorization. Krakend supports fetching the token from cookies with

cookie_key

parameter (https://www.krakend.io/docs/authorization/jwt-validation/), so I guess it must possible to make it work with Supertokens http-only cookies. Theoretically, I can pass

jwk_url

of Supertokens (https://supertokens.com/docs/passwordless/common-customizations/sessions/with-jwt/get-jwks-and-issuer) to Krakend and set

cookie_key

to

sAccessToken

to make it work. But the jwks endpoint in Supertokens is not available unless I turn on jwt in session recipe, is that right? Because I cannot fetch the jwks endpoint with my current setup where I did not enable jwt in Supertokens.

How about storing user tokens in a redis cache db?