leap_web.git - [leap

Age	Commit message (Collapse)	Author
2017-10-17	fix: destroy invites used to create test accounts	Azul
	Production instances are getting cluttered with invites from test accounts. Instead of marking them as used we will now completely remove them. refers to #8804 refers to #8807\
2017-03-20	Merge branch 'debug/rescue-more-specifically' into 'master'	azul
	make the rescue in account creation less broad See merge request !15
2017-03-10	Adds recovery code to user account	Thais Siqueira
	Related with https://github.com/pixelated/pixelated-user-agent/issues/924 With @aarni
2017-03-07	make the rescue in account creation less broad	Azul
	It was catching errors that should have led to 500s
2016-05-23	rename destroy_identity to release_handles	Azul
	This expresses the intent rather than the implementation. Also replace temp with query refactoring.
2016-04-11	allow monitor auth to create users even if invites are normally required.	elijah

2016-03-28	api tokens - clarify terms: "monitors" are admins that authenticated via api ↵	elijah
	token, "tmp" users are users that exist only in tmp db, "test" users are either tmp users or users named "test_user_x"
2016-02-10	allow user accounts to be re-enabled, and for associated identities to also ↵	elijah
	get re-enabled.
2016-01-31	remove cert fingerprints for disabled users, so that they cannot send email ↵	elijah
	anymore. closes #7690
2015-09-28	Make invite code configurable	ankonym
	Through the config param 'invite_required', providers can decide whether users need to provide an invite code upon signup. The default setting is false.
2015-09-28	Fixed the signup bug that wrongly consumes the invite code.	Aya Jaff

2015-09-28	Make sure codes can only be used once, fix validations	ankonym
	We introduced a count on invite codes to make sure that (at the moment) codes can only be used once. (The code will also allow multi-use codes in the future.) Also, some of our validations weren't validating against the correct data, which is now fixed.
2015-03-17	add support for rotating tokens and sessions databases, and for a special ↵	elijah
	tmp db for test users.
2014-12-23	bugfix: ensure both user and identity documents are destroyed if there is a ↵	elijah
	problem creating the account.
2014-12-15	bugfix: allow deletion of user's identities via api when user is deleted. ↵	elijah
	closes #6550
2014-06-23	Account.create - do a User.new instead of User.create, so that we can report ↵	elijah
	the errors on the object if not saved.
2014-06-17	if identity fails to be created, destroy the user. also, pass through ↵	elijah
	identity errors to user and add identity class hook.
2014-05-29	catch corner cases of account creation	Azul
	Users now always check if their identity is valid. We need to make sure this works if the user is a new record and once it has been persisted. While the user is a new record the identity will have no user_id. Old identities that are left to block the login of a user who canceled their account also have a blank user_id. They still should render the new identity invalid so the user can't be saved with a login that has been reserved. Once the user has been persisted we set the user_id on the identity and save it too when creating an Account. This allows us to create a plain user and save it and it will still have an in memory identity only. But the default is to create the user by means of creating an account so an identity will be created as well.
2014-05-28	bring back the alias functionality in Identities	Azul

2014-04-08	moving users: app and test files	Azul