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?

Whats the difference between having

thirdpartyemailpassword

recipe compared to having both

emailpassword

+

thirdparty

recipes? I dont quite understand the

thirdparty

email part, isn't the email/ password auth handled by me? Specifically asking because Golang backend has both

emailpassword

and

thirdpartyemailpassword

recipes

Hey I am using the supertokens core with mysql hosted on amazon RDS. I have changed the config.yaml file and provided the database credentials of amazon's rds. But while doing

supertokens start

it shows me an error

Hi, I've been trying to get the first and last name from the google social login to sync over to supertoken. Is there some kind of configuration needed or how can I solve it? Peeking at the code it looks like it fetches the profile from google, but it only seems to sync the email? https://github.com/supertokens/supertokens-node/blob/master/lib/ts/recipe/thirdparty/api/implementation.ts#L142 Thanks!

I tried setting some data using merge access token payload on the backend and then useSessionContxt to get the payload on the frontend. I am able to set the data properly on the backend but when I try to get it on the frontend it is always an empty object {}. Any idea why?

This may be a bit of a basic question, but in some cases the supertokens instance is not found even though I initialize Supertokens as the first thing in the app. Now I am trying to get the user count in a request handler, and it is saying that Supertokens is not initialized :/

await supertokens.getUserCount()

My session keeps expiring I tried adding the frontend SDK to all of my pages but it doesn't seem to work

Fair, but it fails on me with the cookies

Hi team I'm running into a new CORS error we haven't had in the past. The CORS configuration is now blocking requests between our api (express) and client (react) with the error message: "Access to fetch at 'https://vms-api.macleanengineering.com/auth/signin' from origin 'https://vms.macleanengineering.com/' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled." We've set out cors configuration according to the user/password user guide so I'm starting here. Here's our current cours config: app.use(cors( { origin: ['https://vms.macleanengineering.com/'], allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()], credentials: true, } ));

Is anyone here interested in helping me figure out adding ssl to my supertokens server? I'm trying to use the superTokens docs