Using supertokens-python + flask. I'm using @verify_session(session_required=False). When the token expires I get a 401. Is this desired behavoir?

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'm using Nextjs and embedding the forms in different pages. I've noticed that the forms are taking a while to show up. I suppose this is due to the ssr=false in dynamic?

Hi, im trying to implement supertokens as microservice by esm, but i get this. What is a problem?

Do you have a timeline for C# .net 6 support?

Is it possible to have the users in your own database? If no, do you recommend to have a relation to the supertokens user, from your own database?

Hi, I am getting a blank screen in react if there is an error in the backend during authentication or if the backend is down. Is there any way to do a redirect to an error page on error?

I'm getting this message all of a sudden, don't know where to debug:

error - unhandledRejection: Error: Initialisation not done. Did you forget to call the SuperTokens.init function?

Just finished the PR for supertokens in hive, gonna take care of the deployment config on Monday, if everything goes fine we are running on supertokens next week 🚀 If anyone is interested in the code you can have a look here, I hope it might be useful to someone 😄 https://github.com/kamilkisiela/graphql-hive/pull/303

Hello, is there a

client_credentials

like alternative on login strategy ? I know there is user/password which can be use but I think have property name like clientId clientSecret it would be better. What I want is be able to do machine2machine auth. https://auth0.com/blog/using-m2m-authorization/ this is an example