Re: [Django] #33712: Changing a default auth implementation to use email instead of username. (was: Auth with Email)
Django
------------------------------+--------------------------------------
Reporter: ChathuraGH | Owner: nobody
Type: New feature | Status: closed
Component: contrib.auth | Version: 4.0
Severity: Normal | Resolution: wontfix
Keywords: auth allauth | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* type: Cleanup/optimization => New feature
* has_patch: 1 => 0
* resolution: => wontfix
Comment:
Thanks for this ticket, however, it is a set of various proposition, some
duplicates, some are "wontfix" without a proper discussion and reaching a
consensus on the DevelopersMailingList.
> 1) default method should be email + password.
> 2) Email verification methods should also be included and managed by
settings
> 3) method should be changeable by settings(uName+password ,
email+password , uName , password ,any other)
Django has pluggable authentication backends and you can achieve this by
following the
[https://docs.djangoproject.com/en/dev/topics/auth/customizing/ docs],
it's duplicate of #7591.
Changing a default implementation would be backward incompatible, so first
we have to reach a strong consensus on the DevelopersMailingList. A clear
deprecation path is also required ("wontfix".)
> 4) if possible Allauth default integration (with methods like :- normal
auth(without admin) , normal+admin auth )
Using `django-allauth` is already possible and I don't see any advantages
in including it in Django itself ("wontfix".)
--
Ticket URL: <https://code.djangoproject.com/ticket/33712#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.