Hey all, is there a way with Supertokens to handle account management ? I have multiple users with different roles (admin, user) linked to one account. These users can only retrieve data from entries linked to that account. Pretty common for B2B apps. How do you deal with that ? Thanks a lot

anyone had difficulty deploying SuperTokens-Core to Digital Ocean? The logs mention that

Started SuperTokens on 0.0.0.0:3567 with PID: 26

but then the instance crashes almost immediately.

roles quesiton

Digital ocean deployment issue

hi! why sometimes SuperTokens prints

Failed to fetch

?

Hi, I use localhost for local development at front and remote server at backend api. So when Im trying to connect that way by social, emailpassword or passwordless I get 401 error for endpoints. I think thats because localhost has another cookies domain and server cant get shared them. And the question is: how can i effectively connect from localhost at front to server at back to organise my local development and to make everything work fine?

Hey, I have added a custom field to the backend (nodejs) using the guide on the website, now it looks like it’s expecting the field to be present on signin as well, how can I make it signup only field?

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 ?

Hello, I'm using

updateAccessTokenPayload

to update the the session payload and it shows the new roles when I check the JWT cookie

sAccessToken

in the browser. However when I run

await Session.getAccessTokenPayloadSecurely()

in a Next.js frontend, I still get the old values even when I see the new cookie. It only seems to update when I log out and back in and a brand new session being generated. Does this function take the values directly from the cookies or somewhere else?

Frontend access token payload not updating

Hi, we currently use an older self hosted version of supertokens (react (supertokens 0.15) frontend + python backend) with the email + password recipe. Is it possible to migrate that setup to the passwordless recipe? (I couldn't find anything in the docs on how to migrate between different recipe types)

Migration to passwordless

Can I customize SMS content using Supertokens paid service?

Customising sms for paid service

For passwordless recipe implementation using web-js-sdk It's not clear from the docs which fn should I use. There are multiple fn is SDK reference. So I'm just guessing from the fn names that probably these are all the steps/code I need to have for authentication 1. Create passwordless code -

superTokensPasswordless.createCode({ email: "john@example.org" })

2. Now either they will type in the code in a form I provide or they will visit the email link. If they visit the link, I will get their code like this

const userInputCode = superTokensPasswordless.getLinkCodeFromURL()

3. Then I will verify the code -

superTokensPasswordless.consumeCode({ userInputCode: "8465AWETA" }).then((res) => { if(res.createdUser){ console.log(JSON.stringify(res.user))} })

Session should be automatically set now Am I missing anything?

hi! can i override how

<EmailPassword.EmailPasswordAuth>

from 'supertokens-auth-react' redirects to auth? i want to add a query param

Issue with request session payload @nkshah2

hi.. how to pass a header in Thirdparty.signinup({}).. tried options: { requestInit: { headers: { "x-referral-code": localStorage.getItem("referral"), }, }, }, but this doesnt work.. and also this ThirdParty.init({ preAPIHook: async (request) => { request.requestInit.headers["x-referral-code"] = localStorage.getItem("referral"); }, }),

Hey All, I'm storing custom sign up fields in the user metadata and I want to put them in the access token payload. So I override the signUpPOST and the createNewSession ... the issue is that on sign up the user metadata is still empty for the createNewSession method and so the access token on the frontend will not contain the metadata fields. Is there a way to bypass this? Maybe on post sign up on the frontend, refresh the token explicitly ? Is that possible ? thanks

Modifying session in sign up

What can be happening to not load the css?

No Css issue

Hi, I'm trying to setup auth with my chrome extension, I've browsed past questions about this problem, and it seems the most straightforward solution is to use jwt with localstorage. But there's a couple things I'm still wondering: - I've tried setting the

cookieSameSite

option to none, and I can see that it is indeed set with the option, however, when launching request from the extension, the cookies are not there, why is that the case ? - If choosing to use the jwt with localstorage approach, does it mean that refresh the session does not work anymore ?

With brower extension

https://pub.dev/packages/supertokens does this support web? and can i make custom ui for login in flutter? if yes any resources/example app will be helpful

hi! i know i can add additional fields in sign up page. but can i make them of different type? i need a radio or select input for users to select a role

Hey, quick question. How does the supertoken handling the parallel refreshToken rotatation? I mean, when the refresh token need to roatated. And there's 2 parallel request doing this. One of the will invalid (assuming the token is saved in browser cookie) does it have a grace period or something?

Handling of parallel refresh token requests

Hey, I was trying to edit the signup error msg: "Email already exists. Please signin instead.", but I havent figured out where this can be overwritten. Any help would be appreciated.