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.

Hi, I followed the nestjs setup guide and when I went to auth/dashboard it showed a server error. Nest app shows this error: SuperTokens core threw an error for a GET request to path: '/apiversion' with status code: 401 and message: Invalid API key. The connection uri and api key in nest are the ones provided in the managed service, I don't know what could be wrong.

I am getting a weird issue on refresh. The auto refresh works on get requests but not put/post requests.

Hi there! Here's the issue I'm facing. I'm at the step where I've deployed FastAPI to an AWS Lambda function via Mangum, with Supertokens successfully running (returns hello from /hello), the Lambda function accessing the API database, and the frontend accessing the API. All of these are tested. Unfortunately, I get a cryptic error in the post-signup handler:

response = await api_implementation.sign_up_post(
  File \"/var/task/app/users/utils.py\", line 93, in sign_up_post
    response = await original_sign_up_post(form_fields, api_options, user_context)
  File \"/var/lang/lib/python3.9/site-packages/supertokens_python/recipe/emailpassword/api/implementation.py\", line 199, in sign_up_post
    result = await api_options.recipe_implementation.sign_up(
  File \"/var/lang/lib/python3.9/site-packages/supertokens_python/recipe/emailpassword/recipe_implementation.py\", line 123, in sign_up
    response = await self.querier.send_post_request(
  File \"/var/lang/lib/python3.9/site-packages/supertokens_python/querier.py\", line 167, in send_post_request
    return await self.__send_request_helper(path, \"POST\", f, len(self.__hosts))
  File \"/var/lang/lib/python3.9/site-packages/supertokens_python/querier.py\", line 246, in __send_request_helper
    raise_general_exception(e)
  File \"/var/lang/lib/python3.9/site-packages/supertokens_python/exceptions.py\", line 25, in raise_general_exception
    raise GeneralError(msg) from None
supertokens_python.exceptions.GeneralError

Now, I've tried running the same FastAPI locally (sans Lambda), passing the same Supertokens instance and same API database in production (just the API running locally in uvicorn). I was able to successfully create a new user! Then, I was able to successfully sign in as that user via the frontend hitting the Lambda API 🤯 This tells me that the Lambda function does have access to the Supertokens deployment for signin functions, but mysteriously fails for signup.

Is it possible to give custom userId to supertokens.? I know supertokens uses uuid. I was taking a look at the override functions. Wondering if I can pregenerate the user_id that will be used in supertokens table

Hi everyone. We're currently reviewing Supertokens and Auth0 for our use case but I am not sure if Supertokens can satisfy our needs so I thought to ask here. We're building an integration platform e.g. like Zapier. For example, our user wants to connect (aka authenticate) their typeform and slack accounts with us so that they can send a slack message whenever a typeform receives a new submission. We need to authenticate those services and store the access_tokens securely so that we can make API requests on behalf of our users. Is that something that Supertokens can help us with? More specifically, can I add as many OAuth IdP as we want + securely store access/refresh tokens? Thanks

Hey, i got a little problem after enabling email verification at EmailPassword recipe.

javascript
EmailPassword.init({
  emailVerificationFeature: {
    mode: "REQUIRED"
   }
})

I noticed this every time when i signup successfully i received two email verification email instead of one. I started to digging why this is happened and i added the createAndSendCustomEmail option to my backend setup

typescript
EmailPasswordNode.init({
  emailVerificationFeature: {
    createAndSendCustomEmail: async (user, emailVerificationURLWithToken) => {
      console.log(user, emailVerificationURLWithToken);
    }
  }
})

The callback fired 2 times after every successful signup. I assume the root of the problem is with my frontend setup because it is the only one who is calling my backend. Do you have guys any idea what i did wrong ? 😅

How about storing user tokens in a redis cache db?

Hi all, we put together some scripts to migrate users (along with userid mapping, roles and metadata) from one supertokens deployment to another. Hope it can be useful to some of you 🙂 https://github.com/Solgt/supertokens-migration

Getting the following error when trying to send a verification e-mail:

[INFO] 05:38:57 ts-node-dev ver. 2.0.0 (using ts-node ver. 10.9.2, typescript ver. 4.9.5)
API Server listening on port 3001
Error: 140384285034368:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

where my smtp settings are:

ts
let smtpSettings = {
    host: "mail.privateemail.com",
    authUsername: "no-reply@website.com",
    password: "password",
    port: 587,
    from: {
        name: "Website No Reply",
        email: "no-reply@website.com"
    },
    secure: true
}

Tried switching to port 465 as well but that times out the connection w/ a 504 error and has the following server side error after 2 minutes:

Error: Connection timeout
    at SMTPConnection._formatError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:790:19)
    at SMTPConnection._onError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:776:20)
    at Timeout.<anonymous> (/app/node_modules/nodemailer/lib/smtp-connection/index.js:235:22)
    at listOnTimeout (internal/timers.js:557:17)
    at processTimers (internal/timers.js:500:7)

I tried testing it in java like so and this does work: Ran some [tests]() on . so not sure what I'm doing entirely wrong on the NodeJS back end not sure if relevant at all but I am using NameCheap's mail service (

privateemail.com

) with the DNS handled through Cloudflare. Followed the instructions Namecheap provides [here]() & [here]() Hope that's everything you might need to assist me with my issue