Can I share tokens somehow between subdomains? So let's say I have app.todolists.io and admin.todolists.io so I can do some user management or whatever in the adminpanel. Can I share my login between those two apps so I don't have to reauthenticate? (and maybe I would have an account.todolists.io for language and theme preference for example, or to enable 2fa in the future ;-))

I am testing a service using a hosted production supertokens using a valid sms key, and I need to perform OTP sign in many times. However all of a sudden I stopped receiving sms messages and there are no logs in the console. I am wondering if this could be due to some default spam detection or if this could be due to some rate limiting against my phone number?

Hello, I am trying to break my overrides out to be more modular, but I am having trouble typing them.

ts
import { db } from '@db/index';
import { users, profiles } from '@db/schema';

const thirdPartySignInUpOverride =
  (originalImplementation) => async (input) => {
    let response = await originalImplementation.thirdPartySignInUp(input);

    if (response.status === 'OK') {
      let { id, emails } = response.user;
      console.log('USER SIGNED UP', id);
      await db.transaction(async (trx) => {
        await trx.insert(users).values({
          id,
          email: emails[0],
        });
        await trx.insert(profiles).values({
          userId: id,
        });
      });

      // This is the response from the OAuth 2 provider that contains their tokens or user info.
      let providerAccessToken = response.oAuthTokens['access_token'];
      let firstName =
        response.rawUserInfoFromProvider.fromUserInfoAPI!['first_name'];

      if (
        response.createdNewRecipeUser &&
        response.user.loginMethods.length === 1
      ) {
        // TODO: Post sign up logic
      } else {
        // TODO: Post sign in logic
      }
    }
    return response;
  };

export default thirdPartySignInUpOverride;

I am really not sure of what the

originalImplementation

type should be. I have tried creating an interface from ThirdPartyPasswordless recipe, but that didn't work at all. Any ideas? Edit: Found a way to type using RecipeInterface. Not sure if this is documented? I had to search in discord and got lucky

Hi Supertokens Team, I hope this message finds you well. I am currently working on integrating Supertokens into my application, which consists of Vue.js on the frontend and Nest.js on the backend. Initially, I successfully implemented the Supertokens login functionality using the SaaS version, and everything worked smoothly. To facilitate local development, I decided to switch to the Docker version of Supertokens by setting up a local instance and updating the connectionUrl accordingly. After successfully completing the setup, including table creation, both the Supertokens core and database containers appear to be running correctly on my local environment. However, upon switching the backend's connectionUri to the local URL, I encountered an issue. The login form displays as expected, and I can successfully log in with Google authentication. However, instead of being redirected to the application's homepage, the Supertokens session refresh logs continuously appear, causing an infinite loop. When I revert the connectionUri to the SaaS version, everything functions correctly. I've attached a portion of the logs generated endlessly on the frontend for your reference. Could you please provide guidance on what might be causing this issue? Any insights or suggestions would be greatly appreciated.

Hi, I'm having an issue - sign in and up doesn't work in browser Incognito mode

Hi, I have nodejs app with react. On the deployement domain, the application works perfect. Also, on the localhost it works perfect. But, I have a react developer that only has the react app. The app is pointing to the deployment server because I cant install the entire app at his computer. This way he can develop client side features without the server complexity. The problem is that the react is at

localhost:9001

the remote server is at

domain.com

. he is able to login, and immedietly after the redirection to the success page he gets disconnected. I assume It is because we operating the app under 2 domains

localhost:9001

and

domain.com

. how can I configure the app info on the client side to supprt that? is that possible to have 2 different domains? Thanks

Hi, is the types for the default translations from the recipes in supertokens-auth-react exported?

When I access the application in firefox, I get an error "Please provide a valid domain name" in the frontendConfig section.

Hey team, I believe there is a bug in the latest python sdk version. The

create_reset_password_link

sdk function calls

get_password_reset_link

with the wrong order of arguments: https://github.com/supertokens/supertokens-python/blob/v0.16.8/supertokens_python/recipe/emailpassword/asyncio/__init__.py#L148-L149 https://github.com/supertokens/supertokens-python/blob/v0.16.8/supertokens_python/recipe/emailpassword/utils.py#L303

create_reset_password_link

gives the recipe_id as the second argument to

get_password_reset_link

and the token as the third argument, but

get_reset_password_link

defines the token as the second parameter to the function and the recipe id as the third parameter. As a result when we call the

send_reset_password_email

the link in the email looks like

/reset-password?token=emailpassword&rid=<actual token>

hey guys, my auth is going very slow in prod - i think my instance needs to be restarted. Anyway someone can help me with this asap?