Is there a way to import a csv? I already have some users in a csv file but currently I can't find a way to migrate it to a production database

How safe is it in general to upgrade within the 3.X version range, especially in terms of the PostgreSQL database schema? If the schema would potentially change, would supertokens guarantee that migrations and adjustments are correctly applied upon startup or would it require manual work? And/or would something like this considered a 3.x -> 4.x change?

Hey! Is it possible to customize the spinner? I wanted to make it look more like the other spinners in my app. 😀

Hi ! There's currently an [issue](https://issuetracker.google.com/u/1/issues/211370835?pli=1) with google OAuth2 that prevents controlling test user access. Is there an easy way to block social sign up from supertokens back end ?

Hi, is there any way to make test users seeder with commands from sdk or with another way?

My stack: Next.js frontend Nest.js backend Postgres 1. Getting Next.js to work with SuperTokens seems easy. However, once the user has logged into the Next.js app and starts making API calls, how does the Nest.js app know if the user has logged in from the API calls? 2. I'd like to store user details such as email, auth provider, etc. on my own Postgres database. Is there some kind of callback that will send a request to my API when the user changes email or a new account has just been created?

I have another architectural question regarding SuperTokens and its Core. How suitable is the solution for use by multiple services? I would like to use SuperTokens to manage users which are authenticated into multiple apps, and plan on using the UserMetadata recipe as well as UserRoles recipe to store permissions, roles and groups (using the metadata as unfortunately groups aren't part of the UserRoles recipe). My question is particularly regarding some features like initializing recipes and creating all the roles and permissions - from what I can tell I just have to call an initialization method in my service and create all those beforehand to avoid issues later, but if I have to do this in every service just to ensure that the data really exists it seems like this isn't the best approach. How would you go about managing users that are accessed by different apps, and was SuperTokens built for this use-case?

Hi, I'm looking for info as I have to choose between cookie based/jwt login. But I cannot find right documentation. I have a multitenant, microservice ecosystem, with multiple (web) frontend apps and multiple apis. Once I login in a single frontend app, I must be authenticated in all frontend apps. I have a dedicated supertokens backend microservice (with core hosted internally) where I actually do authentication. No user is shared between different tenant. I cannot use (and I do not want to do it) supertokens SDK in all my backend microservices exposing api (they are a lot, in many different languages). What's the correct choice?

Has anyone found that when they're logged in with super tokens and the backend is verifying their ID, that after they move off the frontend tab for a bit and come back, the userId is rendered as null on the backend? But then when the frontend is refreshed, the userId is correctly set again

Hey team, how can i get user's email id which they entered in FE, and set it in accessTokenPayload i tried using

userInfo, err := passwordless.GetUserByID(userID)

but it errors out log

text
2024/04/07 21:58:59.624599 superToken.go:187: [Info] User Info: map[_default:map[request:0x1400063f9e0]]
2024/04/07 21:58:59.624630 superToken.go:188: [Info] acces token payload map[iss:http://localhost:4000 st-perm:map[t:1712507339623 v:[]] st-role:map[t:1712507339622 v:[]]]
2024/04/07 21:58:59.636381 superToken.go:98: [Info] 96edb6d9-74ad-4c81-9801-6cdf00b84ec5
2024/04/07 21:58:59.638689 roles.go:94: [Info] Role added to user: &{false} with user_id:96edb6d9-74ad-4c81-9801-6cdf00b84ec5 role: admin