How to load Login URL from Auth0

Get Help
, ,
1

I have integrated Auth0 login before by using ‘WebAuthProvider.init()’ way, but now i have recived a URL from client, and they want to load google sign in page by calling that URL.

I have integrated Auth0 by using followig way.

    WebAuthProvider.init(auth0)
            .withScheme("com.aa.aa")
            .withParameters(dataMap)
            .withAudience(String.format("https:/aa/aa/aa",
                    "aaa")
            .withConnection("google-oauth2")
            .withScope("openid profile email offline_access read:current_user update:current_user_metadata")
            .start(activity, webCallback);

Now i have recived following URL from client. I am unable to understand how to load following URL to launch Goole Sign in page by using Auth0.

https://abc-aa.eu.auth0.com/authorize?
audience=http%1%1f%aa.aa&
scope=profile+email+openid&
response_type=code&
client_id=aaaaaaaaa&
code_challenge=aaaaaaaaa&
code_challenge_method=S256&
redirect_uri=http%1%1f%aa.aalocalhost&
connection=google-oauth2

2

Hey @Naofilms, we actually have a doc that details how to connect your app to Google. When you go to test the connection are you experiencing success or is it running into an error? Thanks in advance!

https://auth0.com/docs/connections/social/google

5

Thanks @James.Morrison, I am getting callback URL mismatch. Should i ask the client who provided me this URL to add my application package name in the project?

6

Following up @Naofilms, during your reseting of your Google Keys for your production app you will be asked to specify your callback URLs. This is important to get the correct communication between your app, Auth0, and Google. You will also need to be sure that the Callback URLs are set correctly on the Auth0 end as well as Google’s side to achieve the desired result. Otherwise we will need to check if the callback error is happening from Google or Auth0. This would give us the next step forward, thanks!

7

Thanks…The issue is fixed

8

I’m glad to hear that the issue has been resolved! Please keep us posted on if you have any questions in the future!