I'd add this to the direction Shai's comment is going (if i've interpreted
Shai's commments correctly);
Some Django components (such as how static files are served) often change
during the production life of a project; the way you auth users almost
never changes, or if it does, it changes once.
Hi Nikhil,
I am not calling the shots here, just a member of the community.
However, if you are suggesting this as a work on a 3rd-party library, I
think your suggestion should be either for something completely new, or
a significant improvement over existing 3rd-party libraries. Libraries
which
Just throwing another idea into the pile whilst we're here.
For a long time I've felt we could more easily support a lot more use cases if
we separated Authentication from Authorization.
The simplest path for this would be to separate credentials (username,
password) from the User record.
Hello,
I am Nikhil Muddamsetty and I want to add a new AUTH library with the
following features.
1 > Custom user model to support phone-number or email or username or a
combination of any of these three.
2 > Traditional Account signup and login
3 > Email verification for traditional signup.
