Hi! One question please: what would be the best implementation for a user with "teacher" role, that wants to create emailpassword users with the role "student" in a customize signup page?

So the dashboard revoke session doesn't work with third party logins? Anyone else experiencing this? EDIT: Manually revoking session in the API works, haven't tested signout yet.

Hi @rp_st User Metadata make the app fail. In a handler we call

console.log('toto1')
  const session = await Session.getSession(req, res)
  const user = await EmailPassword.getUserById(session.getUserId())

  console.log('toto2')

  if (user === undefined) {
    next(new Error('INTERNAL_AUTHENTICATION_ERROR'))
    return
  }

  const { metadata } = await UserMetadata.getUserMetadata(user.id)

It fail after the second console.log and I think it's the UserMetadata that fails it. The init looks like this:

recipeList: [
    UserRoles.init(), // RBAC
    Session.init({ cookieDomain: `.${process.env.CLUSTER_HOST ?? ''}` }), // initializes session features
    UserMetadata.init()
  ]

Also when this occurs our pods logs this:

/app/node_modules/supertokens-node/lib/build/recipe/emailpassword/recipe.js:204
        throw new Error("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 Recipe.getInstanceOrThrowError (/app/node_modules/supertokens-node/lib/build/recipe/emailpassword/recipe.js:204:15)
    at Object.getUserById (/app/node_modules/supertokens-node/lib/build/recipe/emailpassword/index.js:72:33)
    at file:///app/dist/endpoints/save_shipping/post/controller.js:18:38
    at Generator.next (<anonymous>)
    at fulfilled (file:///app/dist/endpoints/save_shipping/post/controller.js:4:58)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Hi, do you support managed solution implementation?

So I implemented the "disable sign up/implement invite flow" and it works. But I want to change Supertoken's submitNewPassword component title to instead of a "Change Your Password" to "Set Password" since it makes sense in a invite flow. I looked at the doc and found embed in a page but when I do that for some reason it reloads the url to not having the reset token in the url. so it ends up showing the Reset Your Password component and the user needs to enter their email again which is not right. I am using Next.js I tried looking into the ResetPasswordUsingToken but all it says was:

declare const ResetPasswordUsingToken: (prop?: any) => JSX.Element;

It looks like I can pass in a prop but I don't know what props I can pass or not. I don't know if I am even in the right path. If there is anyway to change the text I am grateful.

hello, im getting an error while creating roles. const response = await UserRoles.createNewRoleOrAddPermissions('free', [ 'read', ]);

Hi, I have a problem with the Session.sighout function. After calling Session.signOut, the session still exists (Session.Session.doesSessionExist returns true). This is the code of my signout function:

javascript
await Session.signOut();
alert(await Session.doesSessionExist())

I am using the supertokens web sdk. Is there anything i did wrong?

Hey I'm trying to setup the backend on AWS lambda. Currently we had it running on ECS. I have followed the ST documentation for Lambda setup and it seems to be incomplete as I'm new to lambda. I have created the layer and uploaded per the documentation and created 2 files (auth.js, config,js) but the Lambda is configured to index.handler which doesnt exists. What change should I make to get it working?

Hi, can anyone tell me how to verify the JWT token?

Hi, there. I'm trying to implement Sign In with Google using the following instruction https://supertokens.com/docs/thirdpartyemailpassword/custom-ui/thirdparty-login. But when I call

thirdPartySignInAndUp

after redirect it throws me error `Error: No instance of ThirdPartyEmailPassword found. Make sure to call the ThirdPartyEmailPassword.init method. `But, actually, it was successfully initialised as I was able to call getAuthorisationURLWithQueryParamsAndSetState to generate auth url. Any ideas what I'm doing wrong?