I want to use supertokens with AWS API gateway+lambda functions I tried following the recipe https://supertokens.com/docs/emailpassword/serverless/with-aws-lambda/backend-config for the backend config, the tutorial says " Create a config.js file in the root directory of your project. " All I have are bunch of lambda functions called from API gateway. Where do I create these files? 🤔

Hey guys. I had a question about the sendPasswordResetEmail method that we use to send a reset password link to the user. Can someone explain the different options available for how the email is sent? I checked the docs here https://supertokens.com/docs/web-js/modules/recipe_emailpassword.html#RecipeFunctionOptions but it isn't clear to me what the RecipeFunctionOptions object passed to recipe functions represents. Maybe an example of the options object and what it means can be helpful.

When I try to use the use functions in the frontend (Angular)

ts
// login function
  async login(email: string, password: string) {
    console.log(
      await ThirdPartyEmailPassword.emailPasswordSignUp({
        formFields: [
          {
            id: 'email',
            value: email,
          },
          {
            id: 'password',
            value: password,
          },
        ],
      })
    );
  }

I get 404 error, stating that the route in the backend (NestJS) does not exist

POST http://localhost:3333/api/signup 404 (Not Found)

. What am I supposed to do, in order for the backend to to the correct think on those routes?

My stack: Next.js frontend Nest.js backend Postgres 1. Getting Next.js to work with SuperTokens seems easy. However, once the user has logged into the Next.js app and starts making API calls, how does the Nest.js app know if the user has logged in from the API calls? 2. I'd like to store user details such as email, auth provider, etc. on my own Postgres database. Is there some kind of callback that will send a request to my API when the user changes email or a new account has just been created?

hey :). we are having an issue with the redirect uri returned for Apple on the web. the code that creates the redirect uri uses the API base path instead of the UI base path.

Hello! I am trying to implement OTP in my Android app but the SuperTokens object isn't saving the session information. I am wondering if I initialized SuperTokens incorrectly (or something else) SuperTokens.Builder(applicationContext, apiDomain) .apiBasePath("/api/auth") .build() I can hit apiDomain on my local machine so we can assume this is correct I can see all the session data that I want in the response in logcat but I somehow can't access it in the SuperTokens object

Hello, I have a question about my use-case that I'm exploring. For the app that I am working on, I have three components: - Web Frontend Application (React+Vite) - Backend Application (NestJs) - Mobile Application (React Native) And I have to support two types of authentication: Email+Password, Passwordless (Using SMS, for mobile application). I am more interested to self-host it, but my other partner wants to use the cloud version. I have some questions for cloud version: - How does the pricing work? if I have 5001 MAU, would my bill be $100 or $0.02? - Since we have the use-case of sending SMS, is it handled by Supertokens in the pricing? - How easy is it move from self-hosted to cloud and vice-versa? - How good is the support if we end up using the cloud version? - When we sign up user with email password, we take multiple inputs apart from email, password, first name, last name. Additional inputs would be company name, tax id, city, phone number. Is it possible to extend the signup form with additional inputs? Thank you to whoever takes their time to answer this. Really appreciate it.

Heyo there ! 👋 Are those features available for free while self hosting SuperTokens ? - SSO - B2B / API Keys distribution for server to resource server communication / Micro service auth - Authorization through RBAC / Role management - A2F Thanks a lot to anyone who will take time to answer this ! 🙏

hi, i faced an issue.

Error: SuperTokens core threw an error for a POST request to path: '/recipe/accountlinking/user/primary' with status code: 402 and message: Account linking feature is not enabled for this app. Please contact support to enable it.

Hey everyone, I'm facing an issue with my Express backend setup along with Supertokens for session management. Here's a snippet of my backend code:

javascript
import express from "express";
import { verifySession } from "supertokens-node/recipe/session/framework/express";
import { SessionRequest } from "supertokens-node/framework/express";

let app = express();

app.post("/like-comment", verifySession(), (req: SessionRequest, res) => {
    let userId = req.session!.getUserId();
    //....
});

I've added

verifySession()

to ensure that only authenticated users can access the

/like-comment

route. However, I'm having trouble accessing this route from the front-end using Axios. I've wrapped my component inside

SessionAuth

so that logged-in users have access, but I keep receiving a 401 error. Could anyone guide me on how to properly access this route from the front-end using Axios and ensure that the user is authenticated? Thanks in advance!