leap_web.git/users/test/integration/api, branch 0.1.2[leap_web]
using ruby-srp 0.1.5 SRP::Client to wrap user in session2013-02-06T15:16:34+00:00Azulazul@leap.se2013-02-06T15:16:34+00:001bf82535b25cb17c58a196fdaab639040f48e769
Remove public key if the key is passed as nil, but not otherwise.2013-01-31T21:09:00+00:00jessibjessib@leap.se2013-01-31T21:09:00+00:002d330838cf5a763d8de2bea752b4e37cf2caa249
There was a weird case with reloading the user in the test if the public key had been unset.
There was a weird case with reloading the user in the test if the public key had been unset.
A user's public_key is the only attribute they should be able to update via API.2013-01-29T20:09:38+00:00jessibjessib@leap.se2013-01-29T20:09:38+00:00afd5697f17a90654b6c058611896e3542a601ef5
Allow PUT API to update user.2013-01-29T19:42:46+00:00jessibjessib@leap.se2013-01-29T19:42:46+00:0090b64fdffdc33f0204af6ac2e315bd4be6bc200a
using subdomain for api requests properly2013-01-16T12:16:38+00:00Azulazul@leap.se2013-01-16T12:16:38+00:001cf4cc5c8d571b571367a08f5e201be868289ed1
minor: further cleanup - try to leave no record behind2013-01-14T19:02:17+00:00Azulazul@leap.se2013-01-14T19:02:17+00:007b323c5dbd7171cf98f69ca159b5aa2174a5d069
make sure can login twice2012-12-11T12:01:24+00:00Azulazul@leap.se2012-12-11T12:01:24+00:00f3f42086e9f325560444f42c6b54269546114167
serve api version 1 in /1/2012-12-08T15:05:40+00:00Azulazul@leap.se2012-12-08T15:05:40+00:000f36c7931fe04bb3d6a3fd70a25fe1090f48e774
Just a very simple start for now.
Do we want to use the api for the secure remote password auth from js?
Just a very simple start for now.
Do we want to use the api for the secure remote password auth from js?
fixed login error message on wrong username2012-11-26T11:15:54+00:00Azulazul@leap.se2012-11-26T11:15:54+00:00cdda8f095d49cdda94c3527ecb92cb15c300327b