leap_web.git - [leap

Age	Commit message (Collapse)	Author
2014-01-07	Some refactoring, to simplify user model, optimize, and allow messages to be ↵	jessib
	sorted by date (although are not now.) Also, rather than use whenever gem, will have cron job created to call task.
2013-12-31	Add authentication to API, but not sure it is best way.	jessib

2013-12-31	Cleanup of code for messages API and cron job for 1 month payment warning. ↵	jessib
	Authentication still remaining piece.
2013-12-30	Change structure to be more no-sql-y, rather than relational.	jessib

2013-12-24	Catching some corner cases & new tests.	jessib

2013-12-24	Add API tests and some refactoring of messages so we can get a user's ↵	jessib
	messages within the webapp.
2013-12-22	locale prefix support:	elijah
	* set locale based on request header * enforce locale path prefix when current locale is not the default * note: don't use root_path anymore, instead use home_path
2013-12-20	make sure overview link is active on Users#show	Azul

2013-12-16	Add test.	jessib

2013-12-13	make the possible actions for users and admins configurable	Azul
	with tests
2013-12-09	Update tests to reflect using plaintext key.	jessib

2013-11-27	minor: rename test to what it actually tests	Azul
	[skip ci]
2013-11-26	simple validation for pgp key format	Azul

2013-11-26	ignore attempts to empty public_key, refactor	Azul
	refactor: prepare validations of the uploaded pgp keys
2013-11-25	Give 404 error if one goes to /key/user for non-existing user.	jessib

2013-11-21	Refactoring of code, and tests.	jessib

2013-11-12	Merge pull request #110 from azul/feature/cleanup-expired-tokens	jessib
	Feature/cleanup expired tokens
2013-11-08	fix cornercase of non expiring tokens	Azul

2013-11-08	Token.destroy_all_expired to cleanup expired tokens (#4411)	Azul

2013-11-07	only check number of disabled identities to make test more robust	Azul

2013-11-06	use the account lifecycle from UsersController#destroy	Azul

2013-11-06	integration test for blocking handles after account destroyed	Azul
	has not been run yet.
2013-11-06	refactor: extract method on account test	Azul
	also test one can't login anymore after destroying the account.
2013-11-05	Identity.destroy_all_disabled will clean up disabled identities	Azul
	This is mostly for cleaning up after tests so far. But we might expand this to destroy all identities disabled before a certain date.
2013-11-05	disabled identities to block handles after a user was deleted	Azul

2013-10-30	test helper to expect_logout.	Azul
	Currently it expects both the session and the token to be cleared. This might change. But we'll always have a definition of what it means to logout we can test this way.
2013-10-30	notify user their account was successfully deleted (refs #4216)	Azul
	Also fixes a cornercase when admins deleted their own account. So far they would be redirected to the users list - which then refused access. Now they'll be redirected to the home landing page as well.
2013-10-28	no need to create a user for testing failed login attempt	Azul

2013-10-28	reset button loading... state on error (#4231)	Azul
	including test refactored error display some
2013-10-18	test logging in through the API using python with umlauts	Azul

2013-10-17	blacklist system logins for aliases and logins	Azul
	We blacklist based on three things: * blacklist in APP_CONFIG[:handle_blacklist] * emails in RFC 2142 * usernames in /etc/passwd The latter two can be allowed by explicitly whitelisting them in APP_CONFIG[:handle_whitelist]. We stick to blocking names that have been configured as both blacklisted and whitelisted - better be save than sorry.
2013-09-26	Since local part of email is case sensitive, want to allow remote email ↵	jessib
	addresses with uppercase letters in local part.
2013-09-25	visual feedback when submitting forms (#3164)	Azul
	This also helps with the failing integration test. We needed a way to tell the ajax request was back. Observing the button state now works for that.
2013-09-24	use token auth when accessing the api from webapp	Azul
	One failing integration test still needs to be fixed
2013-09-23	This ensures that email addresses contain only lowercase letters, and that ↵	jessib
	an identity's destination is a valid Email.
2013-09-19	Merge branch 'develop' into feature/only_lower_case_aliases	jessib

2013-09-19	Merge pull request #82 from azul/feature/sessions-expire	jessib
	Feature/sessions expire
2013-09-18	user.account shortcut to Account.new(user)	Azul

2013-09-17	integration tests for session expiry	Azul

2013-09-09	Merge branch 'develop' into feature/only_lower_case_aliases	jessib

2013-09-05	For moment, have identity's address handle aliased from login so we can use ↵	jessib
	LoginFormatValidation. However, this is not how we will want it eventually. One issue is that the errors messages are set on login, rather than the appropriate field.
2013-09-05	Test of failing to add non-local email address as an identity's address.	jessib

2013-09-04	use /login instead of /sessions/new and test successful login	Azul

2013-09-03	Merge pull request #73 from azul/bugfix/3623-teardown-test-data-properly	jessib
	Bugfix/3623 teardown test data properly
2013-09-03	Merge pull request #75 from azul/feature/token-expiry	jessib
	Token expiry
2013-09-03	Merge pull request #76 from azul/feature/3600-visual-feedback-on-failed-signup	jessib
	Ensure json requests get json error response on failure
2013-09-03	Cleanup sessions controller - webapp logs in through the api.	Azul
	So the #create and #update actions were not needed anymore. Also removed the tests
2013-09-03	Account: Composition to handle User and its identities	Azul
	We have a lot of things that act upon a user record and one or more of it's identities at the same time: * Sing up: Create a user and it's initial identity * Rename: Change the username and create a new identity, turn old into an alias * Cancel Account: Remove user and all their identities. In order to keep the User and Identity behaviour isolated but still have a this logic represented in a sinle place the Account model deals with all these things. We could have overwritten the User#create, User#update and User#destroy methods instead. But then we would always create identities, even if we only need a user (for example in tests).
2013-09-03	cleanup records after running user integration tests	Azul

2013-09-03	simplify users_controller_test	Azul