Django-two-factor-auth

Latest version: v1.17.0

Safety actively analyzes 702183 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 4

1.8.0

Not secure
Added
- Support for Django 2.1.
- Support for QRcode library up to 6.
- Translation: Romanian.

Changed
- Replace `ValidationError` with `SuspiciousOperation` in views.
- Change the wording in 2FA disable template.
- Updated translations.

1.7.0

Not secure
Added
- Support for Django 2.0.

Removed
- Django <1.11 support.

Changed
- Do not list phone method if it is not supported (225).
- Pass request kwarg to authentication form (227).

1.6.2

Not secure
Fixed
- Twilio client 6.0 usage (211).

Changed
- Updated translation: Russian.

1.6.1

Not secure
Added
- Support Twilio client 6.0 (203).

Fixed
- `redirect_to` after successful login (204)

Changed
- Updated translation: Norwegian Bokmål

1.6.0

Not secure
Added
- Support for Django 1.11 (188).

Removed
- Django 1.9 support.

Fixed
- Allow setting `LOGIN_REDIRECT_URL` to a URL (192).
- `DisableView` should also take `success_url` parameter (187).

1.5.0

Not secure
Added
- Django 1.10’s MIDDLEWARE support.
- Allow `success_url` overrides from `urls.py`.
- Autofocus token input during authentication.
- Translations: Polish, Italian, Hungarian, Finnish and Danish.

Removed
- Dropped Python 3.2 and 3.3 support.

Changed
- Renamed `redirect_url` properties to `success_url` to be consistent with Django.

Fixed
- Allow Firefox users to enter backup tokens (177).
- Allow multiple requests for QR code (99).
- Don't add phone number without gateway (92).
- Redirect to 2FA profile page after removing a phone (159).

Page 4 of 4

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.