User verification is not working for me. I get the following errors while trying to activate an account. Any help would be appreciated. Thanks for the great product!
Data was not correct!
Please try again!
user: test
password: password
verification code:$2a$04$passwordIlLDCw2mBK.9A.LMNC1cyCiawb/nVv.rY8ZibvAAJkasW
system specs:
Freebsd 4.9-stable
mysql 4.0.16
php-4.3.4
phpGedView 2.61.1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-01-04
Hello Mike,
First off, the username is case-sensitive. Having that cleared up. I tried with the user specified but that doesn't work. The verification code I get is completely different than yours. I would delete the user and create it again, see what happens. What about other usernames? Do they work?
Regards,
Roland
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-01-04
Thanks for the reply.
The only way I can get a username to work is to authorize and verify it through the admin functions. Self verification has not worked for any of the usernames. I deleted and recreated the user with the same resulting code.
How does phpgedview hash the verification code? I am using blowfish for system password encryption instead of md5. Could that be messing up the code?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem is that blowfish produces a longer hashcode (61 characters) and the database table is only set to hold a 50 character string. Edit the MySQL pgv_users table and update the hashcode field to have a bigger length and then everything should work.
I've updated the authentication_mysql.php file in the CVS to use 255 for the hashcode length.
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
User verification is not working for me. I get the following errors while trying to activate an account. Any help would be appreciated. Thanks for the great product!
Data was not correct!
Please try again!
user: test
password: password
verification code:$2a$04$passwordIlLDCw2mBK.9A.LMNC1cyCiawb/nVv.rY8ZibvAAJkasW
system specs:
Freebsd 4.9-stable
mysql 4.0.16
php-4.3.4
phpGedView 2.61.1
Hello Mike,
First off, the username is case-sensitive. Having that cleared up. I tried with the user specified but that doesn't work. The verification code I get is completely different than yours. I would delete the user and create it again, see what happens. What about other usernames? Do they work?
Regards,
Roland
Thanks for the reply.
The only way I can get a username to work is to authorize and verify it through the admin functions. Self verification has not worked for any of the usernames. I deleted and recreated the user with the same resulting code.
How does phpgedview hash the verification code? I am using blowfish for system password encryption instead of md5. Could that be messing up the code?
Hi Mike...
Just checked the registering routines and I can't see where the problem may be???
It seems that everything works fine...
And normally the verification code is only about 10 chars long and doesn't include something like "$password" or so...
Don't know if the userdata is stored else than in the index version if you use mysql???
If so, your problem may be a problem with your mysql database of the users???
Maybe a memory dataoverflow???
Maybe you need to reinstall???
Or upgrade to the latest beta-version???
But this is a question which may be answered better by anyone using the mysql-databases with phpGedView...
bye, Kurt
Mike and Kurt,
The problem is that blowfish produces a longer hashcode (61 characters) and the database table is only set to hold a 50 character string. Edit the MySQL pgv_users table and update the hashcode field to have a bigger length and then everything should work.
I've updated the authentication_mysql.php file in the CVS to use 255 for the hashcode length.
--John
I hope all these non bug list fixes make it in to the bugs fixed list in the release notes :)
That was it. Thanks for the help everyone!