Hello! when i click login on the sign in / sign up screen (with a discord config, thanks not the problem: it works) in the console of the browser it gets a 404 to

http://localhost:8080/auth/authorisationurl?thirdPartyId=discord

though, it just works when i go there manually. why is that and is there a fix?

Hi, I have just enabled SSO and email verification. When I try and sign up with a microsoft email using SSO, it asks me to verify my email, but the email is not sent to my microsoft email. Email verification is working for the regular accounts.

Hi, I'm kind of lost when trying to get session information in

getServerSideProps

with NextJS, my calls to

SessionNode.getSession(req, res)

end up with an error that says

SessionError: Session does not exist. Are you sending the session tokens in the request with the appropriate token transfer method?

I guess something may be wrong with my config. I am not sure whether `config.supertokens.connectionURI`should be an url that points to a supertokens core, or a supertokens backend, but either gives the same result. When looking at my developper console, I see the cookies being sent to my nextjs app. Any advice on how to solve this ?

Hi Everyone. I have a problem regarding sessions that I'm running into I would like to post the complete thing with the code as well. So I will be posting this in parts as a thread. For starters we are a YC startup and we're using SuperTokens' managed instance as our authentication layer. The frontend is based on

Next.js

and the backend is using

Nest.js

I'm looking into SuperTokens for an app I coded using Hono on Node (https://hono.dev/). I see that it's not one of the frameworks that currently have a middleware (like Express or Fastify). I saw in the codebase that there is also a directory for a "custom" framework but couldn't find any documentation on how it's supposed to be used. Would it be a good way to integrate with Hono or should code the middleware for Hono taking the one from Express as example ? Would it be an interesting contribution ?

hi! I am very baffled about the django documentation. I want to build the equivalent of this in Django DRF: https://passwordless.demo.supertokens.com/auth/ This seems like some half-finished thing that does nothing except report unauthorized at : https://github.com/supertokens/supertokens-python/tree/master/examples/with-django/with-thirdpartyemailpassword And this appears to be a generic description of how to setup django auth and has nothing particularly to do with Super Tokens: https://supertokens.com/blog/django-bootstrap-login-template I don't get it. Does Super Tokens work with Django Session or DRF JWT middleware or not?

We have begun trying to add supertokens to our application and ran into a hiccup. We run our application stack on Cloudflare (CF) workers infrastructure. While they do have a nodejs compatability mode, they do not support all of nodejs apis. https://developers.cloudflare.com/workers/runtime-apis/nodejs/ The nodejs software you provide has dependencies for which they don't have support, like zlib (we didn't get too deep into a full list). Is there any chance of getting a library that is cloudflare compatible?

hello every one, since 3 days i'm try to integrate Supertokens to my distributed app(the frontend is with Vuejs and the backend is with flask) i'm starting the whole system with docker-compose en using supertoken Email-Password + Social. it starts without problems, but when the users are redirected after the login process i become an error in the frontend(something went wrong) and an Exception in the backend(supertokens_python.exceptions.GeneralError: No SuperTokens core available to query). please do someone have any idear on how to fix that?

Hey all, Any idea how to implement SuperTokens with Chrome extensions? I am stuck trying to get it to work.

Hello guys, I am using Supertokens with MongoDB Backend, I have configured everything according to the Docs, And now when I try to SignIn, I am shown "Something went Wrong" Error. So I have checked the Logs from the docker container, and I see the attached errors. I am able to verify that both key_value pair, and jwt_signing_keys collections are created. Also attaching the supertokens-core docker compose config for your reference: supertokenscore: container_name: supertokenscore image: registry.supertokens.io/supertokens/supertokens-mongodb restart: always networks: - localnw environment: SUPERTOKENS_PORT: 3568 MONGODB_CONNECTION_URI: mongodb://user:password@0.0.0.0:27017 MONGODB_DATABASE_NAME: testdb PASSWORDLESS_MAX_CODE_INPUT_ATTEMPTS: 2 PASSWORDLESS_CODE_LIFETIME: 300000 REFRESH_TOKEN_VALIDITY: 15 ACCESS_TOKEN_VALIDITY: 300 ports: - "3568:3568"