| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2013-07-04 | user tests -- user update has been moved entirely to api controller, so fix ↵ | elijah | |
| tests to reflect this. | |||
| 2013-07-04 | fix user typeahead | elijah | |
| 2013-07-04 | users engine changes - rewrite of the views, separate email settings to a ↵ | elijah | |
| separate controller, make users_controller html only and v1/users_controller json only. | |||
| 2013-04-09 | return token on successful login via api | Azul | |
| 2013-04-02 | send salt on Session#create without srp ephemeral A | Azul | |
| 2013-02-26 | api for sessions fixed | Azul | |
| * now we return the user id on login * allow a destroy request for logging out * added test for api sessions controller | |||
| 2013-01-31 | Remove public key if the key is passed as nil, but not otherwise. | jessib | |
| There was a weird case with reloading the user in the test if the public key had been unset. | |||
| 2013-01-29 | A user's public_key is the only attribute they should be able to update via API. | jessib | |
| 2013-01-29 | Allow PUT API to update user. | jessib | |
| 2012-12-11 | make sure can login twice | Azul | |
| 2012-12-08 | serve api version 1 in /1/ | Azul | |
| Just a very simple start for now. Do we want to use the api for the secure remote password auth from js? | |||
 |
index : leap_web.git | |
| [leap_web] | git repository hosting |
| summaryrefslogtreecommitdiff |