We’re a couple weeks away (mostly load testing) from tagging an official 1.3 version of the Weave Server, but if you have a current installation of the registration API (using mysql) and pull from the hg tip, you’ll need to make a pair of database changes to get things working right:
alter table users change column md5 password_hash varbinary(128);
alter table users add column reset_expiration datetime;
This allows us to do individually seeded hashes of passwords (and there’s code in place to auto-update when someone logs in), and to expire reset codes after 6 hours so that an unused one doesn’t stick around.
There are no changes needed if you are running the minimal server.
Advertisement
April 23, 2010 at 8:54 pm |
Will weave 1.3 support addons sync?
April 23, 2010 at 8:55 pm |
Addons sync is not in 1.3, to the best of my knowledge, though that’s not a server question.
May 31, 2010 at 8:04 pm |
i upgraded my weaveserver-registration to the newest snapshot. Now I get on client side, when i try to registrate after commiting captcha:
“unkown error”
and on apache side:
“PUT /user/1.0/testuser HTTP/1.1″ 500 -
I don’t know, how to fix this. But what I recognized is, all GETs work and this is the only PUT.
please help!
June 1, 2010 at 5:27 pm |
It’s hard to tell without seeing an error log, but check that your mysql create table matches the one at the top of the weave_user/mysql.php
July 1, 2010 at 7:53 pm |
Hello limbo,
did you solved your problem?
I have exactly the same problem.