leap_web.git - [leap

Age	Commit message (Collapse)	Author
2013-08-21	return 204 NO CONTENT on API logout	Azul
	That's the only meaningful response.
2013-07-24	separate signup and settings service objects for user	Azul

2013-07-24	removed email settings controller and views	Azul
	PGP setting has been moved into account settings. It's using the API now issueing an Ajax request without any visual feedback. This obviously is not what we want but it hopefully suffices for uploading gpg keys for testing purposes before the Identity UI is in place.
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?