Custom user model app for Django featuring email as username and class-based views for authentication.
A custom user model app for Django 1.8+ that features email as username and other things. It tries to stay true to the built-in user model for the most part.
The main differences between authtools’s User and django.contrib.auth’s are email as username and class-based auth views.
Read the django-authtools documentation.
Before you use this, you should probably read the documentation about custom User models.
Install the package:
$ pip install django-authtools
Add authtools to your INSTALLED_APPS.
Add the following to your settings.py:
AUTH_USER_MODEL = 'authtools.User'
Add authtools.urls to your URL patterns:
urlpatterns = patterns('', # ... url(r'^accounts/', include('authtools.urls')), # ... )
- Add support for Django 1.9, 1.10, 1.11 (Jared Proffitt #82)
- Remove old conditional imports dating as far back as Django 1.5
- Update readme
- Update various help_text fields to match Django 1.9 (Wenze van Klink #51, Gavin Wahl #64, Jared Proffitt #67, Ivan VenOsdel #69)
- Documentation fixes (Yuki Izumi #52, Piët Delport #60, Germán Larraín #65)
- Made case-insensitive tooling work with more than just USERNAME_FIELD=’username’ (Jared Proffitt, Rocky Meza #72, #73)
- Dropped Django 1.7 compatibility (Antoine Catton)
- Add Django 1.8 compatibility (Antoine Catton, Gavin Wahl, #56)
- Backwards Incompatible: Remove 1.6 URLs (Antoine Catton)
- Backwards Incompatible: Remove view functions
Added Django 1.7 compatibility (Antoine Catton, Rocky Meza, #35)
LoginView.disallow_authenticated was changed to LoginView.allow_authenticated
LoginView.disallow_authenticated was deprecated.
Backwards Incompatible: LoginView.allow_authenticated is now True by default (which is the default behavior in Django)
Create migrations for authtools.
If updating from an older authtools, these migrations must be run on your apps:
$ python manage.py migrate --fake authtools 0001_initial $ python manage.py migrate
- Add CaseInsensitiveEmailUserCreationForm for creating users with lowercased email address usernames (Bradley Gordon, #31, #11)
- Add CaseInsensitiveEmailBackendMixin, CaseInsensitiveEmailModelBackend for authenticating case-insensitive email address usernames (Bradley Gordon, #31, #11)
- Add tox support for test running (Piper Merriam, #25)
- PasswordChangeView now handles a next URL parameter (#24)
1.0.0 (released August 16, 2014)
- Add friendly_password_reset view and FriendlyPasswordResetForm (Antoine Catton, #18)
- Bugfix Allow LOGIN_REDIRECT_URL to be unicode (Alan Johnson, Gavin Wahl, Rocky Meza, #13)
- Backwards Incompatible Dropped support for Python 3.2
0.2.2 (released July 21, 2014)
- Update safe urls in tests
- Give the ability to restrain which users can reset their password
- Add send_mail to AbstractEmailUser. (Jorge C. Leitão)
- Bugfix: UserAdmin was expecting a User with a name field.
Django 1.6 support.
Django 1.6 broke backwards compatibility of the password_reset_confirm view. Be sure to update any references to this URL. Rather than using a separate view for each encoding, authtools uses a single view that works with both.
Bugfix: if LOGIN_URL was a URL name, it wasn’t being reversed in the PasswordResetConfirmView.
0.1.2 (released July 01, 2013)
- Use prefetch_related in the UserChangeForm to avoid doing hundreds of ContentType queries. The form from Django has the same feature, it wasn’t copied over correctly in our original form.
0.1.1 (released May 30, 2013)
- some bugfixes:
- Call UserManager.normalize_email on an instance, not a class.
- authtools.models.User should inherit its parent’s Meta.
0.1.0 (released May 28, 2013)