leap_web.git - [leap

Age	Commit message (Collapse)	Author
2016-01-31	remove cert fingerprints for disabled users, so that they cannot send email ↵	elijah
	anymore. closes #7690
2015-09-28	Fix several test failures by stubbing invite code validation	ankonym

2015-09-28	Fix test based on actual invite code validation	ankonym

2015-08-07	do not include random cruft in the common name of smtp client certificates	elijah

2014-07-31	use ApiController#anonymous_access_allowed?	Azul
	There are some places where we only want to require login unless you can use EIP anonymously. So far we had an anonymous_certs_allowed? method in all these controllers. Now it's replaced with ApiController#anonymous_access_allowed?. The naming better reflects that there might be other services that allow anonymous use at some point. This also fixed a typo name -> @filename that broke the ConfigsController.
2014-07-17	add translation and fix tests	Azul

2014-07-14	clean up and simplify error responses and test code	Azul

2014-07-12	fix tests and simplify time calculations	Azul

2014-07-11	Added allow_registration toggle.	Folker Bernitt
	- default is true - See issue #5217 - See companion change in leap_platform.
2014-05-26	Merge pull request #163 from azul/feature/3398-save-hashed-token	azul
	hash token with sha512 against timing attacs #3398
2014-05-26	hash token with sha512 against timing attacs #3398	Azul

2014-05-26	fix test to require login	Azul

2014-05-26	change from GET to POST for certs	Azul
	We create them. let's reflect that in the verb.
2014-05-19	minor: fix tests	Azul

2014-05-19	SmtpCertsController, routes and tests	Azul

2014-05-13	adjust tests to new config and method implementation	Azul
	Ticket.is_creator_vlidated? now actually fetches the user from the db and returns false if it does not exist.
2014-04-18	adopt service_level config to platform settings	Azul
	cost -> rate quota -> storage
2014-04-18	change service level configuration strategy	Azul
	The changes to the configuration required some non minor changes to the platform and also added some flexibility we don't require yet - and thus some new possibilities for errors. So instead we still use the allow_..._certs and ..._cert_prefix options. They basically provide the framework in which service levels can operate. The service level configuration will not include the cert prefix anymore. It only states if the service level is rate limited or not. This avoids conflicts between the two configuration options. I also removed the anonymous service level entirely. It was also turning a boolean decision (do we provide anonymous eip or not) into something way more complex. Instead I added the AnonymousServiceLevel class to handle the corner cases for people who are not logged in. Furthermore i renamed the UnauthenticatedUser to AnonymousUser so it matches the Anonymous Service Level nicely. It's also shorter and more intuitive.
2014-04-17	adjust test to service list in config	Azul

2014-04-17	make use of the UnauthorizedUser	Azul
	Null Pattern for current_user - use it to get rid of some conditionals
2014-04-17	initial commit for the service level api	Azul
	:api/service will return a hash of the current users service level This is failiing if the user is not logged in. Instead it should return the service description for an anonymous user.
2014-04-10	move certs into toplevel	Azul
	cleaned up all the engine stuff that was never really used. Afterwards there is not that much left that makes it into the toplevel.
2014-04-08	moving users: app and test files	Azul