@rp_st Hey guys, Do you have an SDK for Remix?

Hello everyone, does anybody encounter this error

{t: "2023-12-22T11:15:13.063Z", message: "middleware: Started", file: "/gateway/node_modules/supertokens-node/lib/build/supertokens.js:145:22" sdkVer: "16.6.5"}
2023-12-22T11:15:13.072Z com.supertokens {t: "2023-12-22T11:15:13.072Z", message: "middleware: Not handling because request path did not start with config path. Request path: /.well-known/jwks.json", file: "/gateway/node_modules/supertokens-node/lib/build/supertokens.js:152:26" sdkVer: "16.6.5"}

Hi, I'm having trouble with enabling email verification in my ThirdPartyEmailRecipe. When I call EmailVerification.sendVerificationEmail() (imported from supertokens-web-js/recipe/emailverification) in my Vue file, I get the error "No instance of EmailVerification found. Make sure to call the EmailVerification.init method. " In the django backend, I do call emailverification.init() in the recipe_list. Do you know what could be going wrong?

What's the best way to manage users (updating user information, resetting passwords) when there are many users? The dashboard doesn't appear to support search and we can't page through 1000s of users…

Hi, I am switching from managed services to self hosted. I am using python django, postgres database and docker. I have added db and supertoken service in my docker-compose.yml file and added connection_uri='http://localhost:3567' . I am getting hello response also if i call GET http://localhost:3567/hello. But I am getting error as "bmerit-api-supertokens-1 | Loading supertokens config. bmerit-api-supertokens-1 | Completed config.yaml loading. bmerit-api-supertokens-1 | Loading storage layer. bmerit-api-supertokens-1 | Loading PostgreSQL config. bmerit-api-supertokens-1 | Loading supertokens version.yaml file. bmerit-api-supertokens-1 | 04 Aug 2023 11:24:27:406 +0000 | INFO | pid: 2a4d173e-cfae-4b4d-9ad4-79486e5e31b6 | [main] thread | io.supertokens.storage.postgresql.ConnectionPool.initPool(ConnectionPool.java:136) | Setting up PostgreSQL connection pool. bmerit-api-supertokens-1 | bmerit-api-supertokens-1 | Setting up PostgreSQL connection pool. bmerit-db-super | 2023-08-04 11:24:27.662 UTC [75] ERROR: relation "apps" does not exist at character 15 bmerit-db-super | 2023-08-04 11:24:27.662 UTC [75] STATEMENT: SELECT 1 FROM apps LIMIT 1 bmerit-db-super | 2023-08-04 11:24:27.693 UTC [75] ERROR: relation "tenants" does not exist at character 15 bmerit-db-super | 2023-08-04 11:24:27.693 UTC [75] STATEMENT: SELECT 1 FROM tenants LIMIT 1 bmerit-db-super | 2023-08-04 11:24:27.705 UTC [75] ERROR: relation "key_value" does not exist at character 15 bmerit-db-super | 2023-08-04 11:24:27.705 UTC [75] STATEMENT: SELECT 1 FROM key_value LIMIT 1 " Please guide me in this.

Hi, guys. Anyone has any experience adding Microsoft OAuth? Can you share some workarounds if there are needed please? Just starting out, trying to avoid common mistakes

my frontend keeps attempting to refresh even though i just logged in

Hey there, back with another few questions. 😇 I am planning the upgrade from

supertokens-core

v3.16.2

to

v4.0.0

and I have a few questions around the database changes for the

emailpassword_users

and

thirdparty_users

table: Why did you choose

VARCHAR(256)

and

VARCHAR(128)

over just

TEXT

? The latter would have required no database migration and would not require a database migration in the future if the value changes again. Is it safe for me to use

TEXT

instead of

VARCHAR(256)

- or does

supertokens-core

do some kind of database schema validation? How did you manage to roll this out in production? In my current understanding it is not possible to apply this migration without locking the full database table and rewriting every single row. Wouldn't it been smarter (and also less "breaking") to follow this strategy: 1. Add a new columns "thirdparty_users"."third_party_user_id_new" and "emailpassword_users"."password_hash_new" 2. Run a script during outside of a migration/lock that copies the values from the old column to the new column 3. Write the super tokens code in a way that it can deal with both the old and new columns for the duration of the copy from old to new column period Right now, for us running the migration will probably not take longer than a few seconds - however, I am concerned that in the future additional breaking database changes will make it harder for us to migrate to the latest versions. Since you probably have much more users running on your hosted solution, I am especially curious on any insights on how you manged this (of course only if it is possible to share that information)!

I have both an electron app and a web app that do different things. When I sign in through the Electron app, the Electron app starts showing the webapp. Where can I change this? So that Electron just goes to its own main renderer.tsx file. I found this: https://supertokens.com/docs/thirdpartypasswordless/pre-built-ui/auth-redirection But not sure how I can differentiate web/Electron.

Solved on my own 🥳 Hi there! I'm working with the

supertokens-node

SDK and a Fastify Mercurius GraphQL server. Having issues getting our context setup and would love some help. I'm using a request from Postman that has the correct

st-access-token

header set, and have my context setup exactly how recommended in the docs. However, the session always returns undefined https://supertokens.com/docs/thirdpartypasswordless/graphql-integration/backend-setup Sorry for not much initial information... lemme know what's helpful and happy to provide anything I can :)