Hi there, I’ve got a question around recipe user id usage for email verification please as I’m not sure if there is a bug in

getUser

or I just don’t understand how user id mapping is supposed to work between recipe user ids and external ids. Currently we’re mapping our users to an external id with

createUserIdMapping

after signing them up. We then verify their emails using the external id as it’s the id returned by calling

getUser

. Once the email is verified, a row is added to

emailverification_verified_emails

with the external user id as the

user_id

in the database. This works well as the email verification claim

st-ev

is

true

in the access token jwt and if I call

isEmailVerified

with the external user id converted to a recipe user id then it returns true.
The problem seems to be with

getUser

as it returns a list of

loginMethods

but the

verified

flag is false even though

isEmailVerified

returns true if I check using the same

recipeUserId

and email returned in the login method. The email verification claim for this user is

true

in the access token too. However if I change the logic to verify the email based on the supertokens user id instead, then

getUser

will return the login method

verified

as true but the email verification claim

st-ev

is false. I may be misunderstanding how the different ids are supposed to be used but it seems like

getUser

may be returning the verification status of the email login method incorrectly please?

Getting this error on Google login success. Though login is happening fine.

Error: No access, refresh token, API key or refresh handler callback is set.
    at OAuth2Client.getRequestMetadataAsync (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/google-auth-library/build/src/auth/oauth2client.js:272:19)
    at OAuth2Client.requestAsync (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/google-auth-library/build/src/auth/oauth2client.js:371:34)
    at OAuth2Client.request (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/google-auth-library/build/src/auth/oauth2client.js:365:25)
    at createAPIRequestAsync (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/googleapis-common/build/src/apirequest.js:273:31)
    at createAPIRequest (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/googleapis-common/build/src/apirequest.js:49:9)
    at Resource$Userinfo.get (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/googleapis/build/src/apis/oauth2/v2.js:104:58)
    at Object.<anonymous> (/Users/hitesh/dev/jwt_supertokens_hasura/dist/supertokens_config.js:117:57)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/hitesh/dev/jwt_supertokens_hasura/dist/supertokens_config.js:5:58)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Any suggestions?

Is it a bug, when the user metadata in the dashboard is empty, but it is in the db. Or just not implemented yet because of beta

hi, is it expected that using Supertokens with next.js disables static optimization entirely? Our entire app is protected, so we get this error in the Vercel logs:

Warning: You have opted-out of Automatic Static Optimization due to `getInitialProps` in `pages/_app`. This does not opt-out pages with `getStaticProps`

This causes some strange downstream issues for us, because now everything in our client needs to get rendered via serverless functions

Is there a pricing guidance on upcoming multi-tenant and oauth workflow features? We are in process of revamping very very old .net enterprise code with js.

Is is possible for Frontend(Next js) to get the user meta data ?

Hello, I just integrate supertokens in my django app (backend). I well received tokens on my frontend (simulated with Insomnia). Next step is to integrate supertokens authentication on django authentication backend. Do you have some documentation about that?

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 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