Hi everyone, I need support with django admin page. How do I make default login-password login on admin page work? Or if it is complicated, how do I integrate supertokens auth into django admin page?

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 ;-))

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

I have a Nextjs application in which I have created a backendConfig file. When I use more than one third party clients (as used in this example: https://github.com/supertokens/next.js/blob/canary/examples/with-supertokens/config/backendConfig.ts), the application starts giving an error

Error: The providers array has multiple entries for the same third party provider. Please mark one of them as the default one by using "isDefault: true".

. I am not sure what to do here.

Hey everyone. I'm trying to connect a Unity (game engine) client app with SuperTokens. Is there any documentation, examples or quick start guides on how to use C# on the frontend to authenticate with SuperTokens ?

Is there a way to configure email verification recipe to skip the "continue" button when verifing email and instead go directly to next step?

I am developing at sveltekit/capacitor app... in android everything works ok with regrds to supertokens authentication... but in ios devices, I get a successfull sign-in with a success response from server, but then the once I try to authenticate using the

Session

I get:

No session exists

error. Any ideas?

Hy everyone. I have trouble using tokenTransferMethod: 'header'. I want to ship my react app in a webview on iOS with CapacitorJs. I can't make the webview work with cookies on iOS so I thought I could switch to header based auth. So I just added tokenTransferMethod to my client configuration. The client seams to pick it up since I see the header "st-auth-mode: header" to be sent. But I don't see any header "Authorization" being sent to the server. I also added logging which tells me in the browser following interesting lines:

com.supertokens {t: "2023-04-14T09:32:58.495Z", message: "setAuthorizationHeaderIfRequired: token for header based auth not found", supertokens-website-ver: "16.0.1"}

I'm actually a bit confused. I would expect that the tokens are stored somewhere like the local storage and then attached from there. But they seam to be read from the cookies which should not be used as I stated to use headers. Is it my responsibility to persist the tokens somewhere? Am I missing something?

Hi, I am trying to implement SSO between two rails websites with different domain names, e.g. a.com and b.com . Is SuperTokens the right tool for me? We want a phone-password login. Do I just use the

with-phone-password

react example code on each site, or do I need another site like c.com to let the user redirect to for authentication? And how do configure to let it know which domains should share the same session? Sorry I'm quite confused.

Hi SuperTokens 🚀, I ran into an issue with CORS when I tried to integrate your ThirdPartyEmailPassword recipe to my application. My Vue.js frontend app is running at "http://localhost:8888" and the NestJS backend api server at "http://localhost:3000". I followed thoroughly your integration guide for NestJS, however after long hours of search, I cannot figure out how to make the CorsMiddleware run before the Supertoken middleware. I get the following CORS error when a request is sent to one of the supertoken core endpoint. Access to fetch at "http://localhost:3000/auth/signup/email/exists?email=johndoe@gmail.com" from origin "http://localhost:8888" 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'. Here is my main.ts code: async function bootstrap() { const app = await NestFactory.create(AppModule); app.enableCors({ origin: ["http://localhost:8888"], allowedHeaders: ['content-type', ...supertokens.getAllCORSHeaders()], credentials: true, }); app.useGlobalFilters(new SupertokensExceptionFilter()); await app.listen(3000); } bootstrap(); Supertoken config in the **app.module.ts**: @Module({ imports: [ AuthModule.forRoot({ connectionURI: "http://localhost:3567", appInfo: { appName: "IMAT Planner", apiDomain: "http://localhost:3000", websiteDomain: "http://localhost:8888", }, }), ], controllers: [AppController], providers: [AppService, Client], exports: [AppService], }) export class AppModule {} **auth.module.ts**: export class AuthModule implements NestModule { configure(consumer: MiddlewareConsumer) { consumer.apply(AuthMiddleware).forRoutes("*"); } ... } Can you give me an hint on how to make the CORS middleware run before the Supertoken one ?