Signinup failed

Session refreshing

Auth wrapper in NextJS

Hello, I have a doubt regarding multiple instances on the supertokens core running at the same time? I'm looking at the self-hosted version, and was wondering if I have 3 docker containers running the supertokens core and pointing to the same DB does this create an issue or can I have as many containers running as I need. This is for a High Availability simulations on my side. The full use case is for example putting all my core instances behind a load balancer so I don't have a single point of failure.

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()

Hello, I am planning to use SuperTokens as a self-hosted auth service. I have successfully done the docker setup connected with the DB, but I am wondering for the back-end, I see there are libraries for Node, GoLang, and python, but is there a library for Rust? If not, how can I make Rust be able to communicate with SuperTokens?

I'm using nextjs implementation with supertokens, it's working fine. But do supertokens support SSR with protected page. Does anyone have SSR implementation ??? PS: source code is exactly same as official nextjs implementation

Hi, what version of fastify does supertokens support? Because I have followed the instructions according to here https://supertokens.com/docs/thirdpartyemailpassword/quick-setup/backend, but I get 404 when testing the route /auth/signup

Fastify support

Hi, I am getting CORS error with email password node implementation, when I host it on my ec2. I have both incoming ports open to instance

It works great on my local, just cant get settings correct for ec2

Hey guys, Could you please help me with figuring out where to put

verify_session

wrapper when using

graphene-python

? We are planning to implement GraphQL in addition to REST in our Django app. PS. I am new to GraphQL 🙂 if you think that

graphene-python

library is not a good idea, any advices on how to integrate GraphQL into Django app are appreciated 😁

We have a graphql guide for a node backend. Maybe check that out if it helps.

Hello. Is there a way to call supertokens login APIs from swagger? I want to try them, but in order to do so i need to append the cookies to test the authorized APIs

Hi! I wonder if anyone came across the error "Error while setting header with key: front-token and value: XXXX"? I am running the backend using Nestjs and the express framework under the hood. It happens only occasionally

I'm thinking it could have something to do with express 4. To set headers in express 4: res.set(key,value). But looking at this it seems it tries setting the header with methods res.header and res.setHeader. https://github.com/supertokens/supertokens-node/blob/master/lib/ts/framework/utils.ts

Hi ! I wonder how to check the email is verified at frontend

Hi, calling

await SuperTokens.signOut();

doesn't work. It works before but I don't why it isn't anymore

Hey I have a issue with my capacitor ios app again. Here is the debug log from the phone. It logs in normally and cannot hold session somehow. Any ideas?

Hey guys, does anyone have any idea on how to add an e2e test using puppeteer/playwright/cypress? What I tried was somehow copying the cookie and setting it in the test, it worked but not for long, probably because the refresh tokens are also updated after a fixed time interval. I am using react and passwordless recipe. Any ideas/suggestions/pointers?

End to end testing

There seems to be an issue with signing out. After calling the signOut() method, I cannot access the /login path as it just redirects me back to the / path

Do you have any experience on using SuperTokens behind cloudflare with a reverse proxy? My problem is that somehow my cors origins dont get passed even though I defined them

Found a bug in the React lib! https://github.com/supertokens/supertokens-auth-react/issues/519

I hope it isn't a bother, but I was hoping to learn more about this piece comment from GitHub: > The only issue with the steps you mentioned is that the page the user needs to be redirected to, must have have the same path as the refresh token API (that is provided by us). That path is =

/{apiBasePath}/session/refresh

(

/auth/session/refresh

by default). The reason for this is that the refresh token cookie is restricted to be sent to only that exact path (for security reasons). I was curious to know how this helps security, and how SuperTokens enforces this. I noticed that my Remix trick indeed fails to work unless I have the user visit

/auth/session/refresh

from the browser.

createdNewUser boolean on frontend bug

Refresh token path

Hi, do I need to use verifySession in my APIs even if the lambda authorizer is run before that?

Hi, can I send cross domain cookie to verify a session?