redirect_field_name is not passed to django-allauth-2fa about django-allauth-2fa HOT 3 CLOSED

Following this issue. I would have thought there would be a seamless integration as allauth_2fa is built on top of all_auth. Can authors of the plugin please have a look at this a suggest?

from django-allauth-2fa.

Maybe these could help someone make a PR:

https://stackoverflow.com/questions/58357047/how-to-properly-redirect-from-one-app-to-another-app-in-django

https://stackoverflow.com/questions/31334460/urls-py-redirect-the-page-to-another-app

https://stackoverflow.com/questions/53430519/django-redirect-from-one-app-to-another-apps-page-django

https://stackoverflow.com/questions/28554335/django-redirect-to-a-view-outside-the-app

@falc410 Can you share with us your adapter method where you call get_login_redirect_url?

I see in the django-allauth views.py file has multiple redirect_field_name fields. It seems like the LoginView class of django-allauth may need to change or django-allauth-2fa may need to change to address this (not sure).

When you say you are using BaseRequire2FAMiddleware, is this problem only occurring when using BaseRequire2FAMiddleware as opposed to not using it? Are you doing what the docs say in regards to this BaseRequire2FAMiddleware middleware or are you doing something else? Can you share?

https://django-allauth-2fa.readthedocs.io/en/latest/advanced/#forcing-a-user-to-use-2fa

Correct me if I am wrong, but isn't this issue the same as what PR #99 claims to solve?

Couldn't we use request.GET.next to get what the next value is to ensure that it gets redirected there?

from django-allauth-2fa.

This should have been fixed by #131.

from django-allauth-2fa.