Recheck the connection details again please. We did a migration today again - this is the last time this happens. Sorry for the inconvenience

ok, thanks

Hi, why isn't user_id unique, only user_id CHAR(36) NOT NULL ?

Is there any security reason that migrating all credentialed (email / password) users to a magic link wouldn't be advisable? (Coming from another auth provider with active customers)

I see some messages about account linking feature being worked on. I thought supertokens wasn't doing that because its a security issue? 1. Did you change your mind? 2. I can't find the docs page about account linking. Would you mind posting the link to it if you have it? 3. Would you mind posting any links to external sources that talk about the security implications of this?

Are there any timelines for multi tenant support? I know multiple sub domains are supported but over there basically the same session cuts across.

``onHandleEvent: async (context) => { if (context.action === "SESSION_ALREADY_EXISTS") { // TODO: } else if (context.action === "PASSWORDLESS_RESTART_FLOW") { // TODO: } else if (context.action === "PASSWORDLESS_CODE_SENT") { // TODO: } else { let { id, email } = context.user; if (context.action === "SUCCESS") { if (context.isNewUser) { // Sign up createUser(id, email); } else { // Sign in updateUser(id, email); } } } },``

is it logical to put my user creation / update user api calls here in frontend.js ? because I have an error aborted as if the sending was cut (on firefox)

Hey, just had a bit of a problem with CORS since I had updated my frontend SDK, but forgot about my go-SDK. So the 'st_auth_mode' was not used on the backend... :p My question is this: would it be possible to make https://supertokens.com/docs/community/compatibility-table a bit more easy to find? (for next time)

Hello, Having a question, is it possible to create client and secret credentials to allow en external client to request my own API ?

Hi, Can I overrode email and password validation? I have: emailPasswordSignUp: async function (input) { const existingUsers = await ThirdPartyEmailPassword.getUsersByEmail(input.email); if (existingUsers.length === 0) { const inputWithGoodValues: SuperTokensUsersPipe = { email: input.email, password: input.password, }; return originalImplementation.emailPasswordSignUp({ email: inputWithGoodValues.email, password: inputWithGoodValues.password, userContext: input.userContext, }); } return { status: 'EMAIL_ALREADY_EXISTS_ERROR', }; }, but this is ignoring.

anybody know how to fix this issue when trying to up docker-compose configuration

registry.supertokens.io/supertokens/supertokens-postgresql returns 404

Hi, I'm trying to add frontend api in Next 12: I'm doing like in: https://supertokens.com/docs/thirdpartyemailpassword/nextjs/init but I have: > [PWA] Build in develop mode, cache and precache are mostly disabled. This means offline support is disabled, but you can continue developing other functions in service worker. wait - compiling /_error (client and server)... error - ../../node_modules/supertokens-auth-react/lib/build/authRecipe-shared.js:4:0 Module not found: Can't resolve 'react/jsx-runtime' Import trace for requested module: ../../node_modules/supertokens-auth-react/lib/build/thirdpartyemailpassword.js ../../node_modules/supertokens-auth-react/recipe/thirdpartyemailpassword/index.js ./config/superTokens.tsx ./pages/_app.tsx https://nextjs.org/docs/messages/module-not-found I use next-pwa and when I moved if (typeof window !== 'undefined') { SuperTokensReact.init(frontendConfig()) } to next.config.js /** @type {import("next").NextConfig} */ const withPWA = require('next-pwa'); module.exports = withPWA({ reactStrictMode: true, i18n: { locales: ['en', 'jp', 'pl'], defaultLocale: 'en', }, images: { deviceSizes: [280, 320, 375, 425, 768, 1024, 1200, 1440, 2560], loader: 'default', domains: ['s.yimg.com', 'localhost', 'pfartists.xyz'], formats: ['image/avif', 'image/webp'], }, pwa: { dest: 'public', register: true, skipWaiting: true, }, }); What is reason? 🤔

I'm searching if someone had similar problem but Discord found nothing.

Why in https://supertokens.com/docs/thirdpartyemailpassword/custom-ui/securing-routes is likeComment. instead of getServerSideProps/getStaticProps?

Cause it’s related to api route protection and not server side rendering.

I see. But I can change to SSR method to don't render site if user isn't exist in session?

Yes. See our guide on nextjs SSR please.

Ok. I asked because I have backend in nestjs so in another repositorium so I think I cannot use https://supertokens.com/docs/thirdpartyemailpassword/nextjs/session-verification/in-ssr#1-we-use-getsession-in-getserversideprops🤔

Hi, do I need have frontend and backend in docker? Now I have backend and SuperTokens in docker compose and frontend in another repository and I have cors error: Access to fetch at 'http://localhost/auth/session/refresh' from origin 'http://localhost:3000' has been blocked by CORS policy: Request header field st-auth-mode is not allowed by Access-Control-Allow-Headers in preflight response. My settings: app.enableCors({ origin: [

${process.env.WEB_DOMAIN}

], allowedHeaders: ['content-type', ...supertokens.getAllCORSHeaders()], methods: ['GET', 'PATCH', 'POST', 'DELETE'], credentials: true, }); app.useGlobalFilters(new AuthFilter()); //appInfo apiBasePath: '/auth', websiteBasePath: '', WEB_DOMAIN = http://localhost:3000 Sorry for a lot of questions 😅

My dependences: "supertokens-web-js": "^0.5.0",

I use "web-js" without 'node" and nextjs-cors althrough I use Nextjs because I have backend in Nestjs.

Hey I'm trying to find out a bit more information about how JWT expiry with regards to the refresh token flow. Is all of this seamless so that I'll end up getting new JWT updated every ~1 hour with the refresh flow happening implicitly in the backend? For context, I'm trying to figure out how to properly handle subscriptions with Hasura where the token is only passed during the initial Websocket handshake

I'm trying to customize the look of the supertokens sign in button. In the docs it shows this code which I've implemented. I'm assuming this goes in "frontendConfig". It's not working. What am I missing? Here's the short code in frontendConfig:

return {
    appInfo,
    recipeList: [
      EmailPasswordReact.init({
        style: `[data-supertokens~=button] {
                    background-color: #ff0000;
                    border: 0px;
                    width: 30%;
                    margin: 0 auto;
                }`,
        getRedirectionURL: async (context) => {

Hi, did anyone manage to secure command line applications using SSO with Supertokens ?

Hello ! I try to use import { ThirdpartyComponentsOverrideProvider } from 'supertokens-auth-react/recipe/thirdparty'; to cusomise the signup components but he doesn't work

Also i want to know if it's possible to change the title into the component

Right now it's "Sign Up or Log In"