Django-allauth-2fa

Latest version: v0.11.1

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

Scan your dependencies

Page 2 of 4

0.7

======================

* Remove more code that was for Django < 1.11.
* Officially support Django 2.0 and Django 2.1.
* Officially support django-otp 0.7.
* Do not include test code in distribution, fix from akx, PR 67.
* Support for more complex user IDs (e.g. UUIDs), fix from chromakey, see issue
64 / PR 66.
* The extension used by the 2FA templates is customizable. Originally in PR 69
by akx, split into PR 71.
* The QR code is now included inline as an SVG instead of being a separate view.
PR 74 by akx.
* A new mixin is included to enforce a user having 2FA enabled for particular
views. Added in PR 73 by akx.
* Passing additional context to the ``TwoFactorBackupTokens`` was broken. This
was fixed in PR 73 by akx.
* A configuration option (``ALLAUTH_2FA_ALWAYS_REVEAL_BACKUP_TOKENS``) was added
to only show the static tokens once (during creation)> PR 75 by akx.

0.6

=====================

* Drop support for Django < 1.11, these are no longer supported by
django-allauth (as of 0.35.0).

0.5

=====================

* Avoid an exception if a user without any configured devices tries to view a QR
code. This view now properly 404s.
* Redirect users to configure 2FA is they attempt to configure backup tokens
without enabling 2FA first.
* Add base middleware to ensure particular users (e.g. superusers) have 2FA
enabled.
* Drop official support for Django 1.9 and 1.10, they're
`no longer supported <https://www.djangoproject.com/download/#supported-versions>`_
by the Django project.
* Added Sphinx-generated documentation. A rendered version
`is available at <https://django-allauth-2fa.readthedocs.io/>`_.

0.4.4

====================

* Adds trailing slashes to the URL patterns. This is backwards compatible with
the old URLs.
* Properly support installing in Python 3 via PyPI.

0.4.3

======================

* Adds support for forwarding ``GET`` parameters through the 2FA workflow. This
fixes ``next`` not working when logging in using 2FA.

0.4.2

=======================

* Reverts the fix in 0.4.1 as this breaks custom adapters that inherit from
``OTPAdapter`` and *don't* override the ``login`` method.

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.