I'm writing microservices in go and want to migrate to using super tokens (self-hosted). What is the "best practice" to authenticate requests on different services? Previously using AWS Cognito which gave me JWKs to validate requests.

Hey, I have a problem wih usiing the passwordless recipe. I am using the python SDK with fastapi in my backend, custom ui (supertokens-web-js) on the frontend and a selfhosted core. All are updated to the latest version. (0.18.7 / 0.9.1 / 7.0). Here be backend config for the passwordless recipe:

python
passwordless.init(passwordless.ContactConfig(
        contact_method='EMAIL'),
        flow_type='USER_INPUT_CODE_AND_MAGIC_LINK',
    )

And this is the rontend config:

ts
import SuperTokens from 'supertokens-web-js';
import Session from 'supertokens-web-js/recipe/session';
import Passwordless from 'supertokens-web-js/recipe/passwordless'

const initSupertokens = () => {
    SuperTokens.init({
        appInfo: {
            apiDomain: process.env.NEXT_PUBLIC_BACKEND_HOST!,
            apiBasePath: "/auth",
            appName: "CM",
        },
        recipeList: [
            Session.init(),
            Passwordless.init({}),
        ],
    });
}

export default initSupertokens

after calling

import { createCode } from "supertokens-web-js/recipe/passwordless";
...
const resp = await createCode({email})

i am getting

res.status = OK

Also my backend loggs:

"POST /auth/signinup/code HTTP/1.1" 200 OK

and returns:

json
{
    "status": "OK",
    "deviceId": "cY1ju3u88Tl7IDYc/JBf3duXTHoTbeAz5ujFr0ThODI=",
    "preAuthSessionId": "2S0TLFvqwGH9jX7KRM-IBnS4oP8nd8e-JkmsB0JnilY",
    "flowType": "USER_INPUT_CODE_AND_MAGIC_LINK"
}

But i am not getting any email. I tested several email addresses.

Is there any documentation on best practices when self-hosting SuperTokens Core? I was thinking if it is feasible to run the core on a Cloud Run service instance. Thoughts?

Does anyone getting a blank screen after signup in supertoken saas?

Hi everyone, I'm trying to add Passwordless authentication using the Prebuilt UI to my React app (using latest versions of

supertokens-auth-react

and

react-router-dom

) but I'm hitting an issue when the app loads:

Uncaught Error: No instance of Passwordless found. Make sure to call the Passwordless.init method

I'm initialising SuperTokens and Passwordless at the root of my application (see thread for code snippets) and I've checked and all the imports resolve to the same module in case they were pointing at different ones and using different contexts so I'm a little confused 😆 . Can anyone point me in the direction of where I might be going wrong please?

Did anyone set up Nuxt 3 + Supertokens? Any thoughts how to stay on SSR? Saw only NextJS in guides

hey guys, I hope you're doing well. I'm reaching out because I've encountered an issue with my Django application that involves the @verify_session() decorator provided by SuperTokens. Here's a snippet of my code:

Ok I am using this example, to access the user role using the jwtpayload, https://supertokens.com/docs/emailpassword/common-customizations/sessions/user-information-front-end. But I run into the error jwtpayload.role is not part of the properties

Hello guys! Anyone here has implemented something like verifySession to secure APIs using Java (springboot)? Is It possible?

I'm running a Supertokens managed instance in production (on my Flask Python backend, which is hosted on Google Cloudrun). Since it's inconvenient to access the dashboard URL through cloudrun, I found I can run my backend locally (with production flags set) and then access the production dashboard at http://localhost:8000/auth/dashboard Is this recommended / might this interfere with the instance running on prod? (e.g. if limited connections to the Supertokens instance is permitted at once)