Hi I am using this example for third party social login http SuperTokens.com #support-questions-legacy

Hi, I am using this example for third-party social...

abhisheksachdeva

09/19/2022, 4:56 PM

Hi, I am using this example for third-party social login https://github.com/supertokens/supertokens-auth-react/tree/master/examples/with-thirdparty I replaced (core's URL)

connectionURI: "https://try.supertokens.com",

with

connectionURI: "http://localhost:8080",

api-server.js

After clicking "**continue with google**", I got redirected to "supertokens.com", then to the google login screen. I don't see any logs in

core

service after initiating the login flow. Is it still sending request to try.supertokens.com somewhere? Why is it redirecting to supertokens.com? Is it hard-coded somewhere?

rp_st

09/19/2022, 5:22 PM

Hey

rp_st

09/19/2022, 5:22 PM

You should see logs in the core assuming that you have restarted the server post making the change

rp_st

09/19/2022, 5:22 PM

The reason it hits supertokens.com is cause you are using our google credentials for logging in. Use your own and then it won’t hit our site

abhisheksachdeva

09/19/2022, 5:24 PM

I restarted but no logs. > The reason it hits supertokens.com is cause you are using our google credentials for logging in. Use your own and then it won’t hit our site But where is the supertokens.com coming from? Because while mentioning creds, we don't mention URL. Is it possible that browser is caching that URL? 🤔

rp_st

09/19/2022, 5:24 PM

Since the flow is working, it’s correctly connected to your local core

rp_st

09/19/2022, 5:25 PM

The google credentials that you are using belongs to us. Those are a special case in which we redirect to our site since our site is registered as the callback on Google’s dashboard.

abhisheksachdeva

09/19/2022, 5:27 PM

Understood now where the supertokens.com is coming from. Let me try again. Thanks

4 Views

Previous Next