Yes because get_or_create_user already expects an encrypted password.
In gluon.tools its is always called as
user = self.get_or_create_user(form.vars)
where form.vars have already passed validation, therefore the password
has already been encrypted.
If you call get_or_create_user yourself in the code, you must not pass
password but
password=db.auth_user.password.requires[0](password)[0]
On Jan 7, 7:26 am, dz0ny <janez.tr...@gmail.com> wrote:
> Hello!
>
> I've discovered following problem when using auth.get_or_create_user
> ({"email":"m...@web.net", "password":"longlongtime"}), the password in
> database isn't encrypted, but stays plain. But when using form
> registration it's encrypted correctly.
>
> Is this right behavior?
--
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to web...@googlegroups.com.
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en.
