Hey there, I'm using supertokens in my NestJS app. I'm looking to have 2 different auth strategies, one for admin users and one for nomal users. I would like to have 2 different routes and 2 different supertokens service to I can customize sign in / signup options on both independently. Here's what I got at the moment: My abstracted identity module, following the supertokens doc:

export class IdentityAndAccessModule implements NestModule, OnModuleInit {
  ...

  static forRoot({ connectionURI, apiKey, appInfo, caslFactory }) {
    const providers: Provider[] = [
     ...
      {
        useValue: {
          appInfo,
          connectionURI,
          apiKey,
        },
        provide: ConfigInjectionToken,
      },
      SupertokensService,
      PrismaService,
    ];

    return {
      module: IdentityAndAccessModule,
      providers: providers,
      exports: providers,
    };
  }

...
}

Then my 2 auth modules, one for normal users and one for admin:

@Module({
  imports: [
    PrismaModule,
    // TODO: config
    IdentityAndAccessModule.forRoot({
      connectionURI: 'http://localhost:3567',
      appInfo: {
        appName: 'WC APP',
        apiDomain: 'http://localhost:3001',
        websiteDomain: 'http://localhost:3000',
        apiBasePath: '/auth',
        websiteBasePath: '/auth',
      },
      caslFactory: AppCaslFactory,
    }),
  ],
  providers: [AuthService, ...oauthProviders],
  exports: [AuthService, IdentityAndAccessModule],
  controllers: [],
})
export class CustomerAuthModule {}

and another one identical but using /admin/auth as base path for both API and website. My problem is that the first module registered in app.module.ts, will be available but not the other one. So /auth/signin works but /admin/auth/signin always return 404. Any idea? I guess it comes from my module being setup as singleton but can't find any way to have multiple instances using its own config

Hey folks, we currently have services hosted on different domains and we are trying to use single authentication service for it. The supertokens core and the backend service interacting with it is on

somedomain.in

while few of the backend services are on

otherdomain.com

. The cookie domain is set to

somdomain.in

and its subdomains due to it frontend web client is not sending cookies in the api requests made to

otherdomain.com

. How can I send the same cookie to

otherdomain.com

. I hope the question is clear, let me know if I need to clarify further.

please link

Hey !!! I am using supertokens python SDK as a backend with a self-hosted core. Whenever we delete the user from the user management dashboard (provided by supertokens) , the user gets deleted from the database tables that are provided by supertokens (in my case, I am using mysql database), but I want to delete the user from my application's external database at the same time whenever we click on the delete user from the dashboard. Is there a way to do it?

docker install how to open admin panel with docker ?

Any reason why CORS would fail with

Access to fetch at 'http://localhost:3000/v1/auth/signin' from origin 'http://localhost:4200' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'.

cors:

app.enableCors({
    origin: "http://localhost:4200",
    allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()],
    credentials: true,
  });

backend config:

{
  config: {
    appInfo: {
      appName: 'app',
      apiDomain: 'http://localhost:3000',
      websiteDomain: 'http://localhost:4200',
      apiBasePath: '/v1/auth',
      websiteBasePath: '/auth'
    },
    connectionURI: 'http://auth:3567',
    apiKey: 'supersecret'
  }
}

frontend config:

apiBasePath: "/v1/auth"
apiDomain: "http://localhost:3000"
appName: "app"
websiteBasePath: "/auth"
websiteDomain: "http://localhost:4200"

EDIT: using nestjs

hey :). we are having an issue with the redirect uri returned for Apple on the web. the code that creates the redirect uri uses the API base path instead of the UI base path.

hey, I am not able to signup using apple, I am using ST apple account, it says connection refused, it was working till yesterday

Is there any chance a function could be added that returns the session found on the server instead of (or in addition to) adding it to the

request

object? (Talking about

Node.js

here.) I'm playing around with

Svelte Kit

. And it seems like they don't give us access to any data tacked onto the request object. I'm trying to figure out if there's a more functional way to get the session instead. 🤔

How is the sIdRefreshToken used? Is it essential? Docs don’t give much detail