Hello 👋 I'm self hosting supertokens using the following docker image:

registry.supertokens.io/supertokens/supertokens-postgresql:9.0.2

Everything works fine locally and on a VPS server with an IPv4 address. However, I am now trying out the set up on a server that only has an IPv6 address and I can not pull the image because it seems like the registry does not support IPv6. Are you aware of this? Is there a plan for it to support IPv6 or am I forced to find another way around this?

Hi, I currently use supertokens-node in my backend using passwordless authentication. When my client enters the OTP code sent via email, Supertokens checks if the entered code matches. If it's different, it throws an error INCORRECT_USER_INPUT_CODE_ERROR, and if the code is correct, it calls the createNewSession method of ThirdPartyPasswordless. I'd like to allow login for my email with the code 000000 always. I tried to override the method that performs this validation but couldn't succeed. I'd like to know which method performs this validation, if it's possible to override it, and how it would look in my code. thanks!

TOTP question - not enabled against Tenant but per individual user. User sets up TOTP Device and verifies. The following is added to metada:

"requiredSecondaryFactors": [
            "totp"
        ]

When user removed the device via device/remove and has no devices linked - should the metada automatically be updated to remove the required 2nd factor?

Hey there, i'm implemanting a creation of user profil on my own database while a user is signin up. The user is created after the originalImplementation of my signup, and use some additional fields. My issue is, if there is an error in my database interaction, the user is still created in supertokens, and I can't do it before the supertokens signup because i need the user id. Is there a way to revert the user creation if is there any error ?

Hello again! Another question: [The Adding fields page from the docs](https://supertokens.com/docs/emailpassword/common-customizations/signup-form/adding-fields) says that it's possible to include extra fields on sign-up (such as display name, location, or age), but then at the very end of the page, it says: "SuperTokens does not store custom form fields. You need to store them in your db post user sign up." When the

signUp

function is called in step 1, where does the

name

,

age

, and

country

go when a user signs up? I'm curious because I want to include an optional display name field in my sign-up form. I can implement storing the extra field (associated with either the user's email or ID) in my own database, but I'm confused as to why adding the field to the configuration is necessary since SuperTokens can't store the field. Thanks again in advance!

Hey there, is there a way to autostart supertokens on ubuntu? After restart it's not automatic

Hello, we're using Supertokens python sdk in an AWS Lambda + FastAPI and it's working great, but now we'd like to use some supertokens functions outside of the API, like getting user id by email, or managing roles directly from other backend processes. I've noticed it's possible if the init function is called beforehand, how would you refactor the documentation lambda code example so Supertokens can be used outside of FastAPI implementation ? Is there anything else to consider for such usage ?

I want to override the SessionAuth's behaviour of checking if the session is present or not and if not redirect to login page. I know I need to modify the overrideGlobalClaimValidators field but I am having troubles finding documentation on it. I don't know what exactly to put. All I know is the authorization part where it checks the roles.

hi @rp_st I test endpoints via postman. For this, I need to refresh tokens at regular intervals. Is there a token for postman that does not require refresh?

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.