-
Notifications
You must be signed in to change notification settings - Fork 19
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
Implement django-allauth #1895
Comments
Maybe django axes need to be configured https://django-axes.readthedocs.io/en/latest/6_integration.html |
We consider to first update django to a more recent version. This PR offers the relevant changes to migrate to django 5 but it requires more testing. |
…template account path for login routs #1895
… and add social login form class #1895
In general, it works now. The missing parts are: I
|
for some reason currently the social login user´s mail is not verified but no error is raised. When someone uses a social login we can assume the mail to be verified. I also migrated the password change form from our current approach to allauth. |
Okay after setting the verification setting to mandatory this works again. I think we set it to optional on purp. but it seems odd to have a unverified user acc. in our database that can act as a verified one. |
Description of the issue
We want to implement #1363 for that we need a more sophisticated login approach that offers openid connect based user authentication. The package django-allauth offers this out of the box.
Ideas of solution
Install https://docs.allauth.org/en/latest/
Check if the new login system can be merged with the django allauth backend.
Workflow checklist
The text was updated successfully, but these errors were encountered: