Aamir Adnan 31f2b205d3 Take care of custom USERNAME_FIELD on Custom User Model ... Django allows to define custom username field through [USERNAME_FIELD](https://docs.djangoproject.com/en/1.9/topics/auth/customizing/#django.contrib.auth.models.CustomUser.USERNAME_FIELD) on custom user model. In that case there will be no `username` field so it is wrong to assume that the username field will always be present. Simplified the `vaidate` as it is safe to use `authenticate` function from `django.contrib.auth` because it takes care of `AUTHENTICATION_BACKENDS` listed in settings. And if `allauth` is in `INSTALLED_APPS` then `allauth.account.auth_backends.AuthenticationBackend` will be there as well.		2016-01-15 05:37:53 +05:00
..
registration	Return token only when verification is mandatory	2016-01-11 22:33:14 +01:00
tests	Merge pull request #145 from mdentremont/topic/131	2016-01-14 23:53:31 +01:00
__init__.py	First commit.	2014-04-30 12:52:05 -07:00
admin.py	First commit.	2014-04-30 12:52:05 -07:00
app_settings.py	Add support for custom Token model	2016-01-02 15:59:06 -02:00
models.py	Add support for custom Token model	2016-01-02 15:59:06 -02:00
serializers.py	Take care of custom USERNAME_FIELD on Custom User Model	2016-01-15 05:37:53 +05:00
urls.py	closes PR #134 and adds same syntax to demo	2016-01-04 16:29:47 -08:00
utils.py	Merge branch 'master' of https://github.com/Tivix/django-rest-auth	2016-01-07 19:56:33 -02:00
views.py	Merge branch 'master' of https://github.com/Tivix/django-rest-auth	2016-01-07 19:56:33 -02:00