I guessing that I can authenticate/authorise an API only application, with API authentication keys with SuperTokens but I'm not sure how. how can I create a API key to use for API requests to my app? I can create users using /recipe/signup but not sure how to create an access token that does not expire

Heyy, We have a nest.js application deployed on Railway. In the frontend we have next.js deployed on Vercel. In the backend CORS is set like this

app.enableCors({
    origin: [
      '*',
      'http://localhost:3001',
      'http://localhost:3000',
      'https://*.vercel.app',
      'https://*.vercel.app/*',
    ],
    allowedHeaders: ['content-type', ...supertokens.getAllCORSHeaders()],
    credentials: true,
  });

But for all the vercel preview builds, we can't test the app because of CORS issues. Any Idea how to fix it.??

hello guys, can i change the language in button or header ?

hello, what do i type here to use my own smtp configuration ? i have an email address with password already if i need to send from that email address

js
EmailPasswordNode.init({
        emailDelivery: {
          service: new STMPService({
            smtpSettings: {
              host: "smtp.office365.com",
              password: process.env.EMAIL_PW,
              port: 587,
              from: {
                name: "",
                email: process.env.EMAIL_ADDRESS,
              },
              secure: true
            },
          })
        },
      }),

Is anyone here who implements supertokens with express backend with custom nextjs UI?

Hey guys, I saw you did an update on the app dir support for NextJS 13. Whats the best way to stay updated for this? I will be gladly testing it out soon!

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?

Hi, Is there an efficient way to migrate data between one supertons instance to another (assuming they are in different versions)?

my frontend keeps attempting to refresh even though i just logged in

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.