You can have a look at how it's done in Auth: https://code.google.com/p/web2py/source/browse/gluon/tools.py#2043.
Assuming you use the CRYPT() validator to hash the passwords, upon login (using a SQLFORM), the submitted password will also be hashed and stored in form.vars.password, so you could compare that to the value stored in the db. Anthony On Friday, August 16, 2013 5:15:12 PM UTC-4, Scott Hunter wrote: > > For historical reasons, I have an appliance which does not use Auth, but > its own table of users. Passwords get stored in a similar way (that is, > using a normal SQLFORM and a password field). How, then, can I verify a > user's password, since I am not using auth & thus do not have (direct) > access to its methods for taking care of this? > > (I realize the best answer would be to use Auth, and it may come t that, > but I was hoping that there was an alternate solution.) > > - Scott > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
