Thanks for the help.
i recognized that we had our own customised auth_user and we missed
IS_NOTEMPTY validation for the password field.
The issue was resolved
On Wed, Jan 11, 2012 at 8:07 PM, Anthony abasta...@gmail.com wrote:
Are you using a custom auth_user table? With the default table, the
Thanks for the help.
i recognized that we had our own customised auth_user and we missed
IS_NOTEMPTY validation for the password field.
The issue was resolved
Note, if you're using the CRYPT() validator (you should be hashing the
password somehow), it takes a min_length argument, so no
I tryed in Version 1.99.3 and it's working ok. When I put a blank password
there's a Too short message.
2012/1/11 VIREN PATEL viren...@gmail.com
Hi,
In register screen if i do not provide password and verify-password still
the user does gets registered.
also able to login with that user.
Even i tried with version 1.99.3 still it registers successfully and also
able to login with that user with blank password
On Wed, Jan 11, 2012 at 2:38 PM, Albert Abril albert.ab...@gmail.comwrote:
I tryed in Version 1.99.3 and it's working ok. When I put a blank
password there's a Too short
Are you using a custom auth_user table? With the default table, the
password field has a CRYPT validator with the minimum password length set
to auth.settings.password_min_length, which defaults to 4.
Anthony
On Wednesday, January 11, 2012 4:19:40 AM UTC-5, Viren Patel wrote:
Even i tried
Hi,
In register screen if i do not provide password and verify-password still
the user does gets registered.
also able to login with that user. any solution to avoid the acceptance of
blank password
Thanks,
Viren
6 matches
Mail list logo
