Hello. Is https://artifacthub.io/packages/helm/graphql-hive-subcharts/supertokens your official Helm repository for Supertokens Core?

Error on deployment I've been self-hosting supertokens core using supertokens-postgresql v4.3 docker image on kubernetes, with relative ease for a while now. Today when I am trying to deploy it on a new cluster I am faced with this error. Any idea what could be wrong? I am not passing any port number, just passing in the API_KEYS and POSTGRESQL_CONNECTION_URI through environment variables.

What caused the crash: com.fasterxml.jackson.databind.exc.InvalidFormatException: Cannot deserialize value of type `int` from String "tcp://10.2.124.128:3567": not a valid `int` value
 at [Source: (File); line: 194, column: 7] (through reference chain: io.supertokens.config.CoreConfig["port"])

Any way to use a "popup" instead of redirecting to another page when using Google Login?

If SuperTokens Core is being hosted locally, is there a way to enforce that calls to it can only come from

localhost

? (That is, only the local web app can make calls to it and no one else.) I know we have the API keys. But theoretically, enforcing that only

localhost

is allowed would add additional safety, right? 🤔

How safe is it in general to upgrade within the 3.X version range, especially in terms of the PostgreSQL database schema? If the schema would potentially change, would supertokens guarantee that migrations and adjustments are correctly applied upon startup or would it require manual work? And/or would something like this considered a 3.x -> 4.x change?

NextJS Session Recipe Documentation

On flutter it is possible to log in with your email/username and password. Then after checking his information, asked for the second authentication factor(example: totp/email/sms)

hello.@rp_st when resetting password, how can I detect if newPassword is the same as old one? supertokens server is selfhosted, and is seperated from api backend. the only receives when resetting password are just password and token.

@rp_st Why does it take time to validate role claim? I signed up a user, added a role got this log

roles.go:94: [Info] Role added to user: &{false} with user_id:702116bc-1a9f-4a1c-b71e-3d74d9c0fce4 role: admin

but i can't call endpoint with role claim validator it eventually works, but i am not sure about the exact time calling this returns role as admin

go
    admin.Get("/auth/role", func(c *fiber.Ctx) error {
        sessionContainer := session.GetSessionFromRequestContext(c.UserContext())

        response, err := userroles.GetRolesForUser("public", sessionContainer.GetUserID(), nil)

        if err != nil {
            log.Errorf("Error getting roles: %v", err)
            return util.ReturnError(c, 500, "Error getting roles")
        }
        return util.ReturnSuccess(c, response.OK.Roles)
    })

Has anyone found that when they're logged in with super tokens and the backend is verifying their ID, that after they move off the frontend tab for a bit and come back, the userId is rendered as null on the backend? But then when the frontend is refreshed, the userId is correctly set again