Hello, sorry to be a bother. I am setting up a 3rd party solution, and I have the button, can then get to the provider, sign in, and come back. This is where I am stuck. I can't figure out what I should come back to. No matter what I seem to do I just end up back on the signin page. Do I need to make a new express route to come back to and somehow set the login there? Or is there a specific supertoken url I'm supposed to come back to? I tried

[url]/auth/callback/[id]

along with many others. Nothing seems to run the

getProfileInfo

function or any other function I can find.

can one integrate supertokens with an existing database? For instance, Im running a prisma client connected to a postgresql db, which has a schema for users. I would love if I could connect supertokens and my db somehow. For more context, Im using prisma to expose a graphql api, which I would like the auth to be used on

Hey @War_Ace when you get the fetch error, does it make an api call to the backend or error out before the api call is actually made?

Hey! I am trying to customise the Signup / Signin forms using the

ThirdPartyEmailPassword

recipe via the

supertokens-auth-react

package. When implementing the

EmailPassword

recipe I can already customise the entire form page (e.g. creating custom backgrounds, images, etc..) like so:``` <EmailPasswordComponentsOverrideProvider components={{ EmailPasswordSignIn_Override: ({ DefaultComponent, ...props }) => { return ( // My custom Signin component ); }, EmailPasswordSignUp_Override: ({ DefaultComponent, ...props }) => { return ( // My custom Signup component ); }, }} > ``` However, when I try to achieve the same using the

ThirdpartyEmailPasswordComponentsOverrideProvider

it seems I can only customise some parts of the form (e.g. footer, etc..). Any suggestions ? Thanks 🙂

capacitor with mobile app header dont add cookies, becasue diffrent url :/, how to fixed this app url

'capacitor://localhost',
    'ionic://localhost',
    'http://localhost',
    'capacitor://',

but api

api.xx.com

for some reason it doesn't add any cookies when leaving this backend ss

does super tokens work with svelte/kit for frontend?

Hello - getting FST_ERR_CTP_EMPTY_JSON_BODY when trying to delete a user from the dashboard. I use supertokens-node 15.0 and a 6.0 managed dev instance

Hello How can I validate authen with supertokens in gRPC in Go (Gin-gonic)? Thank you

hey, I am using a NestJS backend (with Fastify adapter). I've followed the full guide here - https://supertokens.com/docs/session/nestjs/guide (with a self hosted supertokens core). I have the setup mostly working but running into CORS issues. (api listening on

http://localhost:3001

and ui running on

http://localhost:3002

)

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

It looks like the CORS policies are not being applied correctly to the endpoints that supertokens middleware adds, ex. /auth/session/refresh CORS is applied correctly to the rest of my NestJs endpoints and my react UI at localhost:3002 can query all my regular endpoints but any requests to supertoken middleware endpoints fail with the error below (even though the preflight to /auth/session/refresh seems to be successful 204

Access to fetch at 'http://localhost:3001/auth/session/refresh' from origin 'http://localhost:3002' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Heya, I can't find a definitive answer, is it possible to become a OAuth 2 provider with supertokens?