ahhhh, ok tank you. Your post clarify me much woolly things in my mind. So I understand that password field will not be treated in standard manner, and it needs to be managed very carefully. Its purpose is only to store the final encrypted password, isn't it?
On 3 Set, 17:14, Shawn Milochik <sh...@milochik.com> wrote: > You should exclude the password field in your overridden model form. > If you want to have a password added at the time of user registration > then you can add an additional charfield to the form (make sure to use > the "password" widget). You should probably add two such fields so you > can compare them to see if they match. > > Then, you'll override the save() of the modelform to call the > set_password method of the user object. You need to do this because > the password is stored in a three-part string as you see from your > question. You'll need set_password to convert the raw password to this > format. > > That is all assuming users will be registering themselves. If an > administrator will be registering others, manually call the password > reset function upon successful registration, which would cause the > user to receive an e-mail with a single-use link they can use to > select their own secure password. > > Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
