Default login stopped working after Google enabled

  • Resolved auther61

    (@auther61)


    5 years ago

    I’m trying to set up google authentication on my WordPress website.
    I went through all the steps and the confirmation was successful.
    I attempted to login with my google account at the page “/login/?loginSocial=google” and that seemed to work.

    The problem is that once I set all this up, the regular login page now redirects to the homepage, and not the actual login page.
    So when I try to access /login, it once showed the login page.
    Now, it redirects to the homepage of the website.
    “/login/?loginSocial=google” redirects directly to the google auth.

    Can you please assist?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Ramona

    (@nextend_ramona)

    Hi @auther61

    Did you possibly set the “OAuth redirect proxy page” at Global settings > General: https://nextendweb.com/nextend-social-login-docs/global-settings/ ?
    What page did you select? Because this feature requires using a brand new page, that’s not used for anything else but the OAuth redirect flow. So if you set your /login page there, then the “OAuth redirect proxy page” feature disables the access of the /login page unless you’re doing a social login.

    If you need this feature, create a new page and select that new page, and make sure not to use that page for any other purpose.

    Thread Starter auther61

    (@auther61)

    Yes I did set the proxy page, that’s probably the issue.
    The problem is that google auth didn’t work without setting the proxy page, it just kept redirecting me to the /login page.

    So the status is: if I set the proxy page, google auth works, but regular login redirects to homepage.
    If I do not set the proxy page, regular login page works, but google auth redirects to the login page and does nothing.

    How can I solve this?
    Thank you for your support.

    Ramona

    (@nextend_ramona)

    Hi @auther61

    You can keep using the OAuth page, and it’s actually needed for cases, when the /wp-login.php is not available. Just create a new page what you’re not using for anything else.
    So if you want to keep the /login page for the login, you’ll need to create a new page (like /social-login) and set that to be the OAuth login page.

    So your /login page can’t be both the login page and the Oauth login page. It must be a separate page.

    After that make sure to update the Redirect URIs at all set providers API (step 15 for Google: https://nextendweb.com/nextend-social-login-docs/provider-google/#configuration ) ensure that the social login continues to work.

    Thread Starter auther61

    (@auther61)

    @nextend_ramona, thank you.
    So the new page I’m creating is just a blank page then? It’s just a placeholder for the social login?
    Just trying to figure out why is that required, what was special about my implementation that requires it (in addition to the default configurations)?

    Thank you for your time and support.

    Ramona

    (@nextend_ramona)

    Hi @auther61

    Yes, you should just create a new, blank page what you’re not using for anything else but the OAuth flow.
    Basically, yes, it’s just a placeholder.

    The “OAuth redirect proxy page” is needed when the /wp-login.php is not available to handle the OAuth flow. By default the login/registration is handled using the /wp-login.php page, so if it’s not available, both the login and registration will fail.
    The /wp-login.php can be disabled by security plugins or other kind of 3rd party plugins.

    Thread Starter auther61

    (@auther61)

    Worked great, just implemented it, thank you!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Default login stopped working after Google enabled’ is closed to new replies.