Hello, nice to e-meet you all, I was just trying to provide a new db connection to a tenant I previously created (no problem with that), but when I tried to perform https://supertokens.com/docs/multitenancy/new-tenant#providing-additional-configuration-per-tenant > curl --location --request PUT 'http://localhost:3567/recipe/multitenancy/tenant' \ > --header 'api-key: ' \ > --header 'Content-Type: application/json' \ > --data-raw '{ > "tenantId": "customer1", > "coreConfig": { > "email_verification_token_lifetime": 7200000, > "password_reset_token_lifetime": 3600000, > "postgresql_connection_uri": "postgresql://localhost:5432/db2" > } > }' of course with our tenantId, an error occurred:

Invalid core config: Invalid config key: postgresql_connection_uri

can anyone help me?

Hello - I'm using the passwordHashesImport api to import users from Auth0, but would there be a way to set "isVerified" to true during that process?

Hi, i have implemented custom UI with ThirdPartyEmailPassword recipe - react app. i'm getting this error when i try to signin/up with github.

Error: Getting userInfo failed with 401: {"message":"Bad credentials","documentation_url":"https://docs.github.com/rest"}
    at Object.originalImplementation.getUserInfo (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\recipe\thirdparty\providers\github.js:86:23)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.signInUpPOST (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\recipe\thirdparty\api\implementation.js:35:30)
    at Object.signInUpAPI [as default] (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\recipe\thirdparty\api\signinup.js:68:18)
    at Recipe.handleAPIRequest (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\recipe\thirdparty\recipe.js:73:24)
    at Recipe.handleAPIRequest (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\recipe\thirdpartyemailpassword\recipe.js:63:24)
    at SuperTokens.middleware (C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\supertokens.js:195:38)
    at C:\Users\gouta\supertokens-customapp\backend\node_modules\supertokens-node\lib\build\framework\express\framework.js:128:28

anyone faced the same issue and got it resolved kindly share the solution. thanks

is this something that I should create a github issue ticket with?

# This is required since if this is not there, then OPTIONS requests for # the APIs exposed by the supertokens' Middleware will return a 404 @app.route('/', defaults={'u_path': ''}) @app.route('/') def catch_all(u_path: str): abort(404) why is this required from a backend point of view to allow options request

Hey everyone i am using NextJS to build out a webapp i was curious is there anyway that i can use supertokens

Hi, was wondering how would I setup supertokens and websockets? I've already got my supertokens working fine. But I'm wanting to try and incorporate websocket. I'm currently using nestJS as my backend - frontend isn't completed yet but is using Vite (React). I have some basic handlers for my websockets (when someone sends a message), but was wondering how do I setup guards / logging in etc?

Hello, Why can't I import the ui in react

import { getSuperTokensRoutesForReactRouterDom } from "supertokens-auth-react"

It tells me that it can't find a module with that name. Framework : React Vitejs Typescript Additional information: without vitejs, using create-react-app everything works perfectly.

Hy everyone. I have trouble using tokenTransferMethod: 'header'. I want to ship my react app in a webview on iOS with CapacitorJs. I can't make the webview work with cookies on iOS so I thought I could switch to header based auth. So I just added tokenTransferMethod to my client configuration. The client seams to pick it up since I see the header "st-auth-mode: header" to be sent. But I don't see any header "Authorization" being sent to the server. I also added logging which tells me in the browser following interesting lines:

com.supertokens {t: "2023-04-14T09:32:58.495Z", message: "setAuthorizationHeaderIfRequired: token for header based auth not found", supertokens-website-ver: "16.0.1"}

I'm actually a bit confused. I would expect that the tokens are stored somewhere like the local storage and then attached from there. But they seam to be read from the cookies which should not be used as I stated to use headers. Is it my responsibility to persist the tokens somewhere? Am I missing something?

Could someone tell me how I can get the "Continue with Google" button to show up at the bottom instead of the top?