-
Notifications
You must be signed in to change notification settings - Fork 3
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
Replace two_factor with maykin_2fa #189
Labels
Comments
Coperh
added a commit
that referenced
this issue
Jun 7, 2024
Coperh
added a commit
that referenced
this issue
Jun 17, 2024
Coperh
added a commit
that referenced
this issue
Jun 17, 2024
Coperh
added a commit
that referenced
this issue
Jun 21, 2024
Coperh
added a commit
that referenced
this issue
Jun 21, 2024
Coperh
added a commit
that referenced
this issue
Jul 2, 2024
Coperh
added a commit
that referenced
this issue
Jul 2, 2024
Coperh
added a commit
that referenced
this issue
Jul 5, 2024
Coperh
added a commit
that referenced
this issue
Jul 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I thought that this already happened during the Django 4.2 upgrade, but it seems we're still using our django-two-factor-auth fork (this probably also applies to the other components)
https://maykin-2fa.readthedocs.io/en/stable/
The text was updated successfully, but these errors were encountered: