[web2py] Re: Two parallel methods of authenticating users based on Auth class

>From the handbook: Sessions are retrieved before module code is executed and therefore before classes are defined. Therefore user defined classes cannot be pickled. Given that id of registered user is known, instead of creating any user class and instead of enriching it with required attribute

[web2py] Re: Two parallel methods of authenticating users based on Auth class

Hi All, My fault. Web2py handbook says: "Don't store user-defined classes in session" I will have to re-read the basics after not touching framework for a long time (since the luck of troubles). Thanks for your time. Marcin W dniu środa, 30 lipca 2014 14:39:38 UTC+2 użytkownik Marcin Jaworsk

[web2py] Re: Two parallel methods of authenticating users based on Auth class

Hi Massimo, Thanks for your input. Yes, they would receive email, since they have got external (out of google services) email accounts. I realized that I should describe shortly my approach. Most of aplication users will use GaeGoogleLogin. There are only few that will use alternative login met

[web2py] Re: Two parallel methods of authenticating users based on Auth class

Even if you use GaeGoogleLogin the auth_user table contains both id and email (as provided by gmail). Now if you switch from GaeGoogleLogin to local authentication and email everybody a link to reset the password they will not need to register again and therefore they will retain the current id