leap_web.git - [leap

Age	Commit message (Collapse)	Author
2014-11-10	added destroy user to api	elijah

2014-09-04	fixed typo on configs_controller.rb	elijah

2014-07-18	Allow fetching configs if anonymous EIP access is allowed	Azul

2014-07-17	some cleanup of the messages api and cuke feature	Azul

2014-07-14	fix controller refactor and features	Azul
	Also save debug log on failing features
2014-07-14	move fetch_user into module so it can be mixed in	Azul
	We have an ApiController that wants to call #fetch_user. Since we can only inherit from one class i moved fetch_user into an extension.
2014-07-14	send config files from ConfigsController	Azul

2014-07-14	ApiController with API style auth	Azul
	require_login is require_token for the api controller It also skips the verify_authenticity_token before filter. So all Subclasses of the ApiController will only support token auth. Also made the V1::UsersController a bit more strict. Now way for admins to alter other users through the api. We don't support that yet so let's not allow it either.
2014-07-14	send static list of configs for now	Azul
	Also added authentication steps to cucumber
2014-07-14	use cucumber; initial ConfigsController	Azul

2014-07-14	Moved check for allow_registration into filter.	Folker Bernitt

2014-07-11	Added allow_registration toggle.	Folker Bernitt
	- default is true - See issue #5217 - See companion change in leap_platform.
2014-07-09	list identities based on search only	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	store fingerprints with timestamp	Azul
	Only storing the date as that should suffice for normal expiry and is less useful for identifying users by timestamps
2014-05-19	minor: fix tests	Azul

2014-05-19	store cert fingerprint with main user identity	Azul

2014-05-19	SmtpCertsController, routes and tests	Azul

2014-05-13	allow for usernames with dots	Azul
	preparing for #5664 with some test improvements i ran into this issue This commit includes a fix and the test improvements. In particular it adds BrowserIntegrationTest#login - so there is no need to go through the signup procedure everytime you want a user to be logged in.
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	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