[Symbol(Response internals)]: { url: 'https://www.googleapis.com/oauth2/v1/userinfo?alt=json', status: 401, statusText: 'Unauthorized', headers: Headers { [Symbol(map)]: [Object: null prototype] }, counter: 0 } I am using signin using google using my custom ui and my backend is giving this error

TOTP question - not enabled against Tenant but per individual user. User sets up TOTP Device and verifies. The following is added to metada:

"requiredSecondaryFactors": [
            "totp"
        ]

When user removed the device via device/remove and has no devices linked - should the metada automatically be updated to remove the required 2nd factor?

Can we give access to multiple email IDs for same supertokens account? One of my colleagues created the account, but is unable to give me access to it.

Hello, I'm trying to use supertokens selfhosted with multitenancy and dahsboard and I have 2 issues that appeared this week. 1. When accessing the dashbord there is no "add user" button. 2. When trying to use multitenantcy I get an error saying that the feature is not configured or I need a licence. Both of these issues were not happening last week. I was using supertokens core 7 and after noticing the issues I upgraded to version 9 both with postgres.

has anyone integrated supertokens with nuxt3?

Hi, I'm getting an error when trying to follow the instructions for Third Party Email Password, but I keep getting this error :

No instance of ThirdPartyEmailPassword found.

Hi, thank you for inviting me in. My application is using Vite, React and Nodejs, using Supertokens to handle login and sign up. So we send out invitation emails with accept button linking to an address like: myapp.com/invitation/[the project id user got invited to]?email=userEmail@user.com And when click this link open, user would be redirected to the address: myapp.com/signin/?redirectToPath=[the project id user got invited to] Somehow the email param was not showing, any idea why or how I fix it? Thank you!

hi guys, quick question. Using listUsersByAccountInfo method to get user(filtering by tenantId and email). Our set up means that 2 users(EmailPassword and Passwordless) are returned. is there an easy way to retrieve just the EmailPassword user? Worth adding that we dont use account linking

Hey. I am attempting to run a self-managed instance of SuperTokens. It is connected to the CloudSQL instance. To improve on my testing time etc, I decided to compose my backend container & the supertokens core together via docker-compose. My data is stored on a Google CloudSQL instance. Additionally, my express backend is run on port 3000, and the

supertokens-postgres

is run on port 3567. All of this is run on the same network. When I try to send a POST request to

/auth/signin

, I receive a

status 500

. Additionally, in my logs I receive the following error

TypeError: fetch failed
2023-12-22 06:26:56     at Object.fetch (node:internal/deps/undici/undici:11730:11)
2023-12-22 06:26:56     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-12-22 06:26:56     at async sendRequestHelper._a (/usr/src/node_modules/supertokens-node/lib/build/querier.js:51:36)
2023-12-22 06:26:56     at async Querier.sendRequestHelper (/usr/src/node_modules/supertokens-node/lib/build/querier.js:326:32)
2023-12-22 06:26:56     at async Querier.getAPIVersion (/usr/src/node_modules/supertokens-node/lib/build/querier.js:41:38)
2023-12-22 06:26:56     at async sendRequestHelper._a (/usr/src/node_modules/supertokens-node/lib/build/querier.js:85:38)
2023-12-22 06:26:56     at async Querier.sendRequestHelper (/usr/src/node_modules/supertokens-node/lib/build/querier.js:326:32)
2023-12-22 06:26:56     at async Querier.sendPostRequest (/usr/src/node_modules/supertokens-node/lib/build/querier.js:81:40)
2023-12-22 06:26:56     at async Object.signIn (/usr/src/node_modules/supertokens-node/lib/build/recipe/emailpassword/recipeImplementation.js:58:30)
2023-12-22 06:26:56     at async Object.signInPOST (/usr/src/node_modules/supertokens-node/lib/build/recipe/emailpassword/api/implementation.js:450:28)

The

localhost:3567/hello

is reachable and responsive. The other endpoints on my backend are also responsive. Could someone help me with this error please?

Hello, We have are starting to have user unable to reset their passwords. We are using the "invite flow" describe here: https://supertokens.com/docs/thirdpartyemailpassword/common-customizations/disable-sign-up/emailpassword-changes On the screen you can see the password reset page, it is in french but the text doesn't really matter is classic form reset text translated. The red text just informs the user that there was an error. When looking in the network tab of the dev console, we can see that the endpoint called by supertoken is incorrect and different from what it should be. Endpoint called by supertoken with that specific user:

/auth/Public%3E/user/password/reset

What is expected (and hat we are calling when we try to reproduce ) :

/auth/user/passwordreset/

Any idea where this is coming from ?