Is there a way to configure email verification recipe to skip the "continue" button when verifing email and instead go directly to next step?

Hi! I was interested in using Supertokens for a side project. Right now, my strategy is to use the pre-built UI to accelerate setting up the app and then switch to a custom auth UI down the road. Is this an easy switch to make?

Hello, I just integrate supertokens in my django app (backend). I well received tokens on my frontend (simulated with Insomnia). Next step is to integrate supertokens authentication on django authentication backend. Do you have some documentation about that?

Is the email template tied to the SMTPService class? I want to enqueue the email to an HTTP endpoint (also easier to integration test) instead of directly connecting to SMTP

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.

How soon is "soon" ? and it seems like there's still a partial support for mongodb, to what extent can I use it? Can I fully rely on it?

Getting this error on Google login success. Though login is happening fine.

Error: No access, refresh token, API key or refresh handler callback is set.
    at OAuth2Client.getRequestMetadataAsync (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/google-auth-library/build/src/auth/oauth2client.js:272:19)
    at OAuth2Client.requestAsync (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/google-auth-library/build/src/auth/oauth2client.js:371:34)
    at OAuth2Client.request (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/google-auth-library/build/src/auth/oauth2client.js:365:25)
    at createAPIRequestAsync (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/googleapis-common/build/src/apirequest.js:273:31)
    at createAPIRequest (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/googleapis-common/build/src/apirequest.js:49:9)
    at Resource$Userinfo.get (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/googleapis/build/src/apis/oauth2/v2.js:104:58)
    at Object.<anonymous> (/Users/hitesh/dev/jwt_supertokens_hasura/dist/supertokens_config.js:117:57)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/hitesh/dev/jwt_supertokens_hasura/dist/supertokens_config.js:5:58)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Any suggestions?

Hey, does Supertokens work with Capacitor ( https://capacitorjs.com/ ) ?

Hey guys, I want to use krakend.io API Gateway to enforce request level authorization. Krakend supports fetching the token from cookies with

cookie_key

parameter (https://www.krakend.io/docs/authorization/jwt-validation/), so I guess it must possible to make it work with Supertokens http-only cookies. Theoretically, I can pass

jwk_url

of Supertokens (https://supertokens.com/docs/passwordless/common-customizations/sessions/with-jwt/get-jwks-and-issuer) to Krakend and set

cookie_key

to

sAccessToken

to make it work. But the jwks endpoint in Supertokens is not available unless I turn on jwt in session recipe, is that right? Because I cannot fetch the jwks endpoint with my current setup where I did not enable jwt in Supertokens.

I have a FastAPI backend and a NextJS frontend. I want to use getServerSideProps to send the logged in user's data to my frontend. When I try to get the logged in user's data in getServerSideProps, I get { message: 'unauthorised' }. I think this is because the cookies in the browser are not sent to my FastAPI backend. Is this even possible?