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.

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

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 ?

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"

Hey, I've been hit with "`Access to fetch at 'https://[backend-url]/auth/signin' from origin 'https://[frontend-url]' 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`" and I can't really seem to solve it. I'm able to sign up users but not login.

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?

Hi! I am running into a problem on the backend... My sessions are getting created just fine, and I can use them on the frontend without any problems. However, when I try to use the verifySession() middleware in the backend, it is returning

session = undefined

. I suspect that it is a configuration issue. I am using Firebase Functions, and this is a different function (so a different route / endpoint). Still, I have not been able to successfully configure... Any thoughts?

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 ?

I'm having this TypeScript problem when setting up the auth UI in a Next.js app:

users:build: info  - Linting and checking validity of types...
users:build: Failed to compile.
users:build: 
users:build: ./pages/auth/[[...path]].tsx:21:6
users:build: Type error: 'SuperTokensComponentNoSSR' cannot be used as a JSX component.
users:build:   Its element type 'ReactElement<any, any> | Component<unknown, any, any>' is not a valid JSX element.
users:build:     Type 'Component<unknown, any, any>' is not assignable to type 'Element | ElementClass'.
users:build:       Type 'Component<unknown, any, any>' is not assignable to type 'ElementClass'.
users:build:         The types returned by 'render()' are incompatible between these types.
users:build:           Type 'React.ReactNode' is not assignable to type 'import("/Users/james/Code/oughtinc/elicit-mono/apps/users/node_modules/@types/react/index").ReactNode'.
users:build:             Type '{}' is not assignable to type 'ReactNode'.
users:build: 
users:build:   19 | 
users:build:   20 |   return (
users:build: > 21 |     <SuperTokensComponentNoSSR />
users:build:      |      ^
users:build:   22 |   )
users:build:   23 | }

This is when using the Auth component directly from https://supertokens.com/docs/thirdpartypasswordless/nextjs/setting-up-frontend

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?