Releases: relekang/django-nopassword
v4.0.1
v4.0.0
Feature
- Support next in rest (deba82e)
- Add NOPASSWORD_LOGIN_ON_GET setting (627267e)
- Set default html_template_name in EmailBackend (0f46de1)
- Add admin (81a184f)
- Raise error when sending code without backend (8bfe372)
- Use username field metadata for form/serializer fields (8d46122)
- Add rest views (34c1a6b)
Fix
- Use timezone.now() instead of datetime.now() (cf22def)
- Rename LoginCodeRequestView to LoginView (44363c5)
- Rename sms template (a8d1522)
- Change login_code_request_email template extension (efecdcf)
- Fix isort error (e349e5b)
Documentation
v3.0.1
Fix
- Updated the "invalid_login" error message (#72) @ataylor32
Documentation
- Made it so the documentation has all of the settings' default values (#75) @ataylor32
v3.0.0
Fixes
BREAKING CHANGES:
- This release adds namespacing to the urls of nopassword. You must change your includes
to use a namespace. The default namespace isnopassword
, however it can be changed
withNOPASSWORD_NAMESPACE
.
v2.1.1
v2.1.0
2.0.0
Numeric codes
Thanks to @gthomas
- Add option for numeric login codes
- Fix import bug, only import TwilioBackend in nopassword/backends/ini.py if twilio is installed
TwilioBackend
- Add
TwilioBackend
- Support custom code lengths
1.0.0
Rename the app to nopassword: This means that from this version installed apps
in django should list nopassword
not django_nopassword
. In addition all imports
need to point to nopassword
not django_nopassword
.
The possibility to customize code delivery:
Most of the code in the EmailBackend
has been moved to a new backend called
NoPasswordBackend
. The latter is not meant to be used on its own, but it will
make it easier to create other backends similar to EmailBackend
. With other
words, it has become easier to send the login codes with other technologies like
sms.
Verification of the user:
django-nopassword uses user.is_active()
to determine whether a user is still
active or not. In this release we moved this into its own method,
NoPasswordBackend.verify_user
, which makes it easier to create your own logic
to verify your users.
Django 1.7 support: Now it is tested and known to work with the released version
of Django 1.7. Earlier it had just support for the beta 3.
Migrations: Support for both Django 1.7 migrations and South migrations. To use
South it is necessary to use version the lastest version(1.0), since it is the only
version that looks for migrations in south_migrations
.