-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google auth broken in 4.0? #8806
Comments
@Yann-J a part from the blank page does the login complete? If you refersh the page or go to the home page is the user logged in? |
Hey @giohappy sorry I forgot to mention :) No, the login is not complete after the page load. The menus are still clickable and I can still do all the usual anonymous browsing. Also worth noting that this also affects the signup flow, and was tested after wiping all the domain's cookies. |
I suspect that the new client templates are not compatible with django-allauth social logins pages. |
@Yann-J it looks like the new If you set it to True login and sign up should work. |
Indeed, it works well now! Thanks a lot! I guess it still makes sense to keep the ticket opened until either the parameter is added by default, or the templates are updated? But at least there's a clear workaround! |
Expected Behavior
Hello good people! I have a GeoNode/Geoserver setup configured to use Google as auth provider. It has been working well on 3.x throughout various upgrades, but following an upgrade to 4.x the Google login flow seems broken. Login with internal users still works fine.
The
settings.py
section to configure my auth is as follows:I'm also setting the following env vars to valid values - although I also had to configure the OAuth values in the admin UI:
OAUTH2_CLIENT_ID
OAUTH2_CLIENT_SECRET
AUTH_DOMAIN
Actual Behavior
With 4.x, the Google login button is present as expected in the login page. However when pressing it, the browser is redirected to
/account/google/login/?process=login&next=/catalogue/#/
which shows up as a blank page. No HTTP call is ever made to any Google URL.No logs in console (server or client). I couldn't identify any change to the relevant sections of the configuration...
Steps to Reproduce the Problem
Specifications
docker build
from this commitThe text was updated successfully, but these errors were encountered: