That is a bad idea. It leaves your users vulnerable to a server or database or database backup compromise.
The design is that if your server/database doesn't know the password, it can't give it up. If you truly want to store passwords in the clear, you will have to re-implement the authentication back end for yourself. Most of us would feel that it would be irresponsible to help you. Be sure you have a very good reason. You don't, for example, need the clear text of old passwords to prevent a user from reusing an old password: the old hashes are enough. Bill On Wed, Sep 18, 2013 at 11:10 AM, Sivaram R <sivaram2...@gmail.com> wrote: > I have views.py to show the form instance and update the instance. > > On edit the form data,all other field are showing the correct > value,password field is showing the entire hashed value from database and > not the entered password. > > Is any way to show the entered password instead of hashed value in > database. > > forms.py > > class UserRegisterForm(forms.ModelForm): > password = forms.CharField(widget=forms.PasswordInput(render_value=True)) > class Meta: > model = User > > Thanks > > > -- > 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 django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
