Yes I was trying to implement it for learning django properly. Alright , I got your point.
On Thu, Mar 20, 2014 at 9:55 PM, C. Kirby <[email protected]> wrote: > Are you building your own authentication system as a learning opportunity > or to actually use in a production system? If it is for a production system > then...don't. There is quite a bit of code in django Users to handle > passwords and keep passwords safe and authentication secure. > > If you want to expand on the User model or modify it then you should > extend or substitute the existing User model ( > https://docs.djangoproject.com/en/1.6/topics/auth/customizing/#extending-the-existing-user-model > ) > > That page also has information about hooking into different authentication > backends if you want to use an existing source of users (for instance to > use LDAP or the like) > > > > > On Thursday, March 20, 2014 9:06:48 AM UTC-5, Aryak Sengupta wrote: >> >> I am new to Django (but not new to python) and I am looking forward to >> create a customized page using django. I have read about django's inbuilt >> authentication system but I want build it from scratch So here are the few >> ideas I am stumbling upon : >> >> >> 1. Creating a *users* class in the models.py with username and >> password as the fields (both are CharField) >> >> 2. Creating two views one named *LoginView*, which will depict the >> initial login page (such as a *form* imported from a *module named >> forms.py*) and another view named *LoggedInView* which will show >> only the username of the logged user >> >> 3. Mapping them into corresponding URLs >> >> I tried creating it with above mentioned thoughts but I got stuck with an >> error as follows: >> >> Forbidden (403) >> >> CSRF verification failed. Request aborted. >> Help >> >> Reason given for failure: >> >> CSRF cookie not set. >> >> >> I couldn't figure out why possibly I am getting this error for >> incorporating such a simple(and basic) functionality. >> >> *I want to understand the best way/approach to go about this (for >> implementing this functionality). I am not worrying about the error for the >> time being since I didn't spend much time thinking about it (So I am not >> posting any code). I want to get my approach right first. I want to be >> flawless while implementing such basic and elementary stuffs. * >> > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/fa3d5877-2098-4cb0-a2ae-8f503f24d517%40googlegroups.com<https://groups.google.com/d/msgid/django-users/fa3d5877-2098-4cb0-a2ae-8f503f24d517%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CALTbq1wS_feOyHp-b8Yn6ZgRNhB_wHtXpLome5TJA6nar0S0rQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
