Let's say I have two customers, C1 and C2, and we provide some integrations infrastructure to them where Auth is powered by Supertokens (self-hosted for development purposes). Both customers have a common user, U1. If the user signs in to their products P1 and P2 using google, supertokens will assume that it is the same user as

third_party_user_id

is the same but will create two

sessions

. This might lead to some issues in the future as we will be using user_id for lots of other stuff. 1. Is there any way to consider them as separate users? 2. Should we use separate supertokens instance (cloud or local) for each customer? I guess, you will have something internally to manage multiple clients on the supertokens cloud.

Hi, I have an issue with the combined phone/email field. On some browsers the autocomplete adds an extra space at the end of the email address and then when trying to continue the user gets an error that the email is invalid. Did anyone encounter this issue or has an idea how to resolve it? Thanks

Hi, just a question about sessions in react native, should .signout() method delete the session ? Because it is not the case on my implementation and it is a bit of a problem as I am use .doesSessionExist() to determine if the user is signedIn or not

How do the

supertokens-node

verifySession

and

Session.getSession

functions behave in case the session is expired? Do they check this? or will they return `null`/`undefined` in such an scenario?

Hey I'm trying to redirect the user to different url after logging in, its working fine with otp login (to do this i am passing different url in redirectToPath=someUrl), but google login success does not redirect (redirectToPath becomes empty string). following this guide https://supertokens.com/docs/thirdpartyemailpassword/common-customizations/redirecting-post-login i couldn't find something similar with the Session recipe which i would like to support as well

Question - whats the best pattern for implementing a post signup event, and similarly whats the best pattern for fetching the user after signin (in particular if the user data is stored in a different custom table) and adding the user data to the req.session. Effectively when someone signs up I'd like to create a custom user entity in a different table, and then fetch it again whenever the session is created or refreshed and make it available on the request

I get the following error when i try to sign up with a user: Error: No SuperTokens core available to queryError: No SuperTokens core available to query Setup: I am self hosting a core, without docker on my mac. (It should be running, i can get the hello message when visiting /hello) The connection to my postgresql is successful (the default supertokens tables have been generated)

Hi, After adding values for expose_headers to my CORS Middleware (Python/fastApi), the login form (React) is not working anymore. After clicking login, the page refreshes but i am still on the auth page. After removing the expose_headers it works fine.

python
api = CORSMiddleware(
    app=api,
    allow_origins=[
        "http://localhost:3000"
    ],
    allow_credentials=True,
    allow_methods=["GET", "PUT", "POST", "DELETE", "OPTIONS", "PATCH"],
    allow_headers=["Content-Type", SUPERTOKENS_HEADER] + get_all_cors_headers(),
    expose_headers=[SUPERTOKENS_HEADER]
)

The value for SUPERTOKENS_HEADER is

x-st-cookie

but i am still using the default cookie implementaion at this time.

Question about sharing sessions across subdomains...

Hey there! is there a way to customize the email verification form? the same way we can customize signup/signin form