I have both an electron app and a web app that do different things. When I sign in through the Electron app, the Electron app starts showing the webapp. Where can I change this? So that Electron just goes to its own main renderer.tsx file. I found this: https://supertokens.com/docs/thirdpartypasswordless/pre-built-ui/auth-redirection But not sure how I can differentiate web/Electron.

hey @big_bongster does the electron app have its own native login U?

No, the electron app uses React so I am also just using the provided React components

right. So what exactly happens after login?

It loads the web page into Electron, instead of returning to the "/" route of Electron

as in it's opening the browser?

yes

whats the configured websiteDomain?

appInfo: { appName: 'app', apiDomain: GetConfig().apiUrl, websiteDomain: 'http://localhost:3000', apiBasePath:

${GetConfig().apiUrl}/auth

, // websiteBasePath: '/auth', },

on the frontend

on the frontend it's the url of the website

right. I think cause you have set it to localhost, it opens the browser.

That was for electron

hmm.

Yes I copied that and it works great when everything is on localhost. But now I'm trying to deploy and I'm having the redirect issue. I'm fixing something else right now, so after that, I'll try to tinker with this some more. Thanks for your help.

sounds good. Im not quite familiar with electron, so hard to help without having a demo app that can reproduce the issue.

Ok the issue is the callback redirect if I use a social provider. It is redirecting me (I think) to

websiteDomain: 'http://localhost:3000',

. I just copied that from the example here: https://github.com/supertokens/supertokens-auth-react/blob/4b2a650f8ac520a769829c42b8e1d2284cc66025/examples/with-thirdpartypasswordless-electron/src/renderer.tsx#L52 When I use email + OTP sign in, it works fine.

right. I thikn you need to make the social provider redirect to your backend layer, which calls asn API which redirects to your electron app. Not sure, but it be in our demo app.

Ah I see. There's some deeplink protocol and redirect handlers. Complex. I'll try to see if I can get it working. Thanks

yeaaa.. unfortunately providers can't deep link to your app. So this is sort of a workaround. It's there in the example app though.

Hmm, I tried running the Electron example, and I think it might be out of date. If I try to log in using Google, I just see "Cannot GET /auth/callback/google" as the only HTML in the Electron app. I think it is suffering from the same issue where it is getting redirected to localhost:3000. In this case, the server has a handler on "/auth/callback/google" that redirects to the deeplink.

hmm. Can you open an issue about this? We will fix the demo app sometime this / next week.

thanks

Yes, in the issue, I wrote down what my understanding of the desired redirects is

right. So google then needs to redirect you to your api layer, and a route on your api layer which you create (a GET API). Have you done that?

Yeah, I've just copied the example app

gonna take a look soon, will keep you posted @big_bongster

Thank you darko

haven't gotten around to it, but on my agenda today

Cool, thanks!

Not really, but I'm working intermittently on this 🙂

ok sure