Hey, I use docs Nextjs app dir. I added SuperTokens.init() in root layout but I have the error: ``Error: Initialisation not done. Did you forget to call the SuperTokens.init or Session.init function? ``. I don't use backend config and withSession for Nextjs because I've backend in Nestjs. I have this error in sessionUtils file:

let session = await Session.getSession(baseRequest, baseResponse, options);

.

Hello Team, I'm currently in the process of migrating users from a Firebase project that utilizes both social and** password-based** logins to Supertokens, which primarily uses Social and Passwordless logins. The new workflow involves user authentication by Supertokens, followed by the transfer of the received token to MongoDB for verification using a JWK URI. Subsequently, a new user account is created within the MongoDB Atlas Authentication system. I'm seeking advice on how to effectively migrate these social and password-based users. I'm aware that the

recipe/user/passwordhash/import

method can be utilized to migrate Firebase users. However, the destination project is configured for Passwordless logins. Also, the

recipe/signinup

method, which can be used to import social users, does not provide access tokens. This presents a challenge as MongoDB Atlas lacks an admin API for creating users with Custom JWT. Therefore, creating a user in MongoDB requires a valid access token from Supertokens. Your guidance and insights on this migration process would be greatly appreciated.

Hi Everyone, I have a "BFF" with nextjs where the user authenticates and from there I'm proxying some API calls to some services where I need some kind of security, as the proxy sends the cookies I could use the backend SDK to validate and secure this services but I was thinking on just sending the jwt token (is that sAccessToken?) but I found that I do not have the user id in it, where is it stored ? in the session ? What would be a best practice, addit to the super token payload ?

Hi, I'm just getting started with SuperTokens. I would like to integrate it with an existing FeathersJS backend, but there does not seem to be much info. Would love to see an integration guide. It seems it would be pretty closely follow the same themes in the nestjs docs.

Im having an issue with using Supertokens in custom nodejs project. I get the following error ERR_UNSUPPORTED_DIR_IMPORT when I try the following

js
// Super Tokens Library
import supertokens from "supertokens-node";
import Session from "supertokens-node/recipe/session";
import EmailPassword from "supertokens-node/recipe/emailpassword";
import { errorHandler, middleware } from "supertokens-node/framework/express";
// Express Library
import express from "express";
// Cors Library
import cors from "cors";
// SuperToken Configurations
import { getWebsiteDomain, superTokensConfig } from "./config";

What would be the best way to use Supertokens (self-hosted) with a crypto wallet so people could create or recover their Ethereum keys or encrypt the keys with a login. I guess this would only be possible with MPC or Web3 authentication correct? If so is there a roadmap for when this would be coming?

Hi everyone, I am using Supertokens dashboard for viewing users and sometimes for session management for my application. I want to extend the APIs; that the dashboard uses to delete the user, edit name, and revoke session info; for the cases like performing additional checks and DB actions when that dashboard API is hit. How can I do that? I was unable to find relevant documentation here - https://supertokens.com/docs/userdashboard/about My understanding is that it should be similar to api_overrides where we can override the API for Dashbaord. Is this correct? Dashboard APIs - 1. https://app.swaggerhub.com/apis/supertokens/CDI/3.0.4#/Dashboard%20Recipe/getAllSessionsForDashboardUser 2. https://supertokens.com/docs/python/recipe/dashboard/index.html 3. https://supertokens.com/docs/python/recipe/dashboard/api/index.html I have other overrides too for signup and signin. Can dashboard overrides be done and used along with my existing overrides\?

> $0.02 per MAU > Free under 5K MAU Is that 2 cents per user authentication? I'm working on an application for a car parking company and I was planning on doing a passwordless auth approach. Problem is they will likely have about 10,000 different bookings a month and very unlikely that they will log in other than to check their booking. Trying to justify the cost which would be fine if it was for any other kind of system, problem is this is for users that will likely log in once a year if ever.

AWS Lambda fronted by httpAPI Gateway not Working But dev computer backend Does For OTP, both lambda and backend send OTP but providing OTP value in UI results in OTP remaining. No error message or reason given. The code for both Lambda Handler and backend are based on docs and the same. Issue seems to be this:

// For lambda fronted by httpAPI Gateway
...
logger.js:31 com.supertokens {message: "saveTokensFromHeaders: Saving updated tokens from the response headers", supertokens-website-ver: "17.0.0"}
logger.js:31 com.supertokens {message: "fireSessionUpdateEventsIfNecessary returning early because the front token was not updated", supertokens-website-ver: "17.0.0"}

// For local dev computer backend
logger.js:31 com.supertokens { message: "saveTokensFromHeaders: Saving updated tokens from the response headers", supertokens-website-ver: "17.0.0"}
logger.js:31 com.supertokens { message: "saveTokensFromHeaders: Setting sFrontToken: {long token}", supertokens-website-ver: "17.0.0"}

The line of code that has a different is in saveTokensFromHeaders (see https://github.com/supertokens/supertokens-website/blob/469421261802a73ca7439e9de039e7d56e53ca9d/lib/build/xmlhttprequest.js#L815)

// frontToken has a value with backend, but no value with lambda fronted by httpAPI Gateway
frontToken = response.headers.get("front-token");

It feels like the

front-token

HEADER is not getting returned by the lambda fronted by httpAPI Gateway. 2.5 days of trying to figrue this out. Any ideas?

Hello, my react web frontend received 401 error, and do not refresh token. I use fetch. What can be wrong?

js
SuperTokens.init({
  appInfo: {
    appName: 'test',
    apiDomain: AUTH_BASE_URL,
    websiteDomain: APP_DOMAIN,
    apiBasePath: '/auth',
    websiteBasePath: '/auth',
  },
  recipeList: [
    EmailPassword.init(),
    Session.init(),
  ],
})

python in the attached, i have some overrides a lot of text. @rp_st cc