It looks like SuperToken cookies are exceeding the permitted limit. I'm getting this error: "Set-Cookie header is ignored in response from url: http://localhost:4000/auth/session/refresh. The combined size of the name and value must be less than or equal to 4096 characters."

hey @rp_st I am using passwordless. i am trying to do something after user registers. For now I am just printing in the backend after a new regisration. when try to enter a code or use magic link to verify the backend sdk crashes. I tried this override:

Hi, We're authenticating our react app with supertokens react components successfully from SUBDOMAIN.DOMAIN.COM where our frontend lives and where the cookie is also set. Our main API and supertokens fastify middleware live on DOMAIN.COM/API and correctly set cookie and validate the requests The problem we have is that we have another authentication flow where customers will get a new supertokens cookie from DOMAIN.COM, they are supposed to be authenticated but the react auth component does not recognize it. Would you have a cue on how we could solve that?

Hello! We have a little problem about implementation of Supetokens on Ionic/Capacitor. In particular about the native versions of it. Its like if the back-end side doesn't allow customScheme (ex: capacitor://app.id/home). After the basic implementation of docs we have this error on iOS: Unhandled Promise rejection: – "Please provide a valid domain name" Can some help me please? Thanks in advance!

Fair, but it fails on me with the cookies

Super Tokens Core (self-hosted) and postgreSQL: password authentication failed

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

Hi, I'm getting this error when i tried to create a new role through User Management Dashboard

Error: SuperTokens core threw an error for a PUT request to path: '/recipe/role' with status code: 500 and message: Internal Error

Any idea what could be the issue. thanks for the help!

Hello, I have a question about my use-case that I'm exploring. For the app that I am working on, I have three components: - Web Frontend Application (React+Vite) - Backend Application (NestJs) - Mobile Application (React Native) And I have to support two types of authentication: Email+Password, Passwordless (Using SMS, for mobile application). I am more interested to self-host it, but my other partner wants to use the cloud version. I have some questions for cloud version: - How does the pricing work? if I have 5001 MAU, would my bill be $100 or $0.02? - Since we have the use-case of sending SMS, is it handled by Supertokens in the pricing? - How easy is it move from self-hosted to cloud and vice-versa? - How good is the support if we end up using the cloud version? - When we sign up user with email password, we take multiple inputs apart from email, password, first name, last name. Additional inputs would be company name, tax id, city, phone number. Is it possible to extend the signup form with additional inputs? Thank you to whoever takes their time to answer this. Really appreciate it.

hello, I had some question regarding session sharing across subdomains. At the moment im deploying on running on localhost. I have the main domain localhost:3000/ and a subdomain blog.localhost:3000/. The problem im coming across is that when i access the subdomain it redircts me to the login page to login and even if i do login it redirects me back to the login page. The session returns unauthorized. I looked into session sharing and the sessionTokenFrontendDomain i set to ".localhost" but in the caution section of the documentation it says I should not set it to localhost. I instead have indeed declared on my /etc/hosts file the subdomain for blog.localhost. However the problem persists. Am i missing a step? Also do i keep the sessionTokenFrontendDomain with the mention in the hosts file or i remove it?