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-10	Adds recovery code to user account	Thais Siqueira
	Related with https://github.com/pixelated/pixelated-user-agent/issues/924 With @aarni
2016-11-17	bugfix: only send login errors once	Azul
	If a login was invalid as a username but also for the identity we used to have duplicate error messages. Let's avoid that. Also added a test to make sure invite_code errors are properly displayed no matter what other fields are set or missing. Pixelated will rely on this to test invite codes
2016-04-11	allow monitor auth to create users even if invites are normally required.	elijah

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	Fix three unit tests by passing Factory Girl a valid invite code	ankonym
	The tests were failing because of a hardcoded "testcode" string so during test setup we generate a valid code and pass it to Factory Girl
2014-05-13	destinguish user.email from user.email_address	Azul
	use the former if you want a working email account or nil, the latter if you want the email address associated with a given user no matter if the user actually has an email account or not.
2014-04-08	moving users: app and test files	Azul