summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2013-09-05Move handle method to Email model and have it work for local and non-local ↵jessib
emails.
2013-09-05Merge pull request #80 from azul/bugfix/fix-tests-broken-by-route-removalazul
use /login instead of /sessions/new and test successful login
2013-09-04switch submodule to use https:// instead of git:// - NOTE: this requires you ↵Micah Anderson
do a git submodule sync
2013-09-04use /login instead of /sessions/new and test successful loginAzul
2013-09-04fix login form - use api session urlAzul
There's no non api sessions resource anymore.
2013-09-03Merge pull request #73 from azul/bugfix/3623-teardown-test-data-properlyjessib
Bugfix/3623 teardown test data properly
2013-09-03Merge pull request #75 from azul/feature/token-expiryjessib
Token expiry
2013-09-03Merge pull request #76 from azul/feature/3600-visual-feedback-on-failed-signupjessib
Ensure json requests get json error response on failure
2013-09-03Merge pull request #79 from azul/cleanup/remove-outdated-controller-actionsjessib
Cleanup/remove outdated controller actions
2013-09-03clearify usage of V1::UsersController#index for autocompleteAzul
[skip ci]
2013-09-03use the login logout named route instead of sessions resourceAzul
The main part of the sessions resource now lives in the API. the two named routes are just fine for what is left.
2013-09-03remove email aliases controller - we don't use it anymoreAzul
2013-09-03Cleanup 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-03remove unneccessary user creation and destruction in ticket testAzul
2013-09-03remove the user after integration testing customer creationAzul
2013-09-03different tests need different namesAzul
2013-09-03do not leave behind users in billing unit and functional testsAzul
2013-09-03Account: Composition to handle User and its identitiesAzul
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-03cleanup records after running user integration testsAzul
2013-09-03simplify users_controller_testAzul
2013-09-03don't leave id records behind when unit testingAzul
2013-09-03expire token according to config setting auth:token_expires_afterAzul
2013-09-03use Token#authenticate for authenticationAzul
This will return the user. But we can add timestamp validations and updates here.
2013-09-03integration test for displaying internal server error during signupAzul
2013-09-03Test the error handling of json and html responsesAzul
2013-09-03Ensure json requests get json error response on failureAzul
Normally rails sends an html page which can't be parsed by the client.
2013-09-02Merge pull request #78 from jessib/finish_removing_email_settings_referencesazul
Remove references to email_settings controller, which has been removed. ...
2013-09-02Remove references to email_settings controller, which has been removed. An ↵jessib
identities controller will replace it.
2013-09-02Merge pull request #77 from azul/feature/3522-configurable-logfilejessib
add config setting for logfile
2013-09-02Merge pull request #74 from azul/refactor/finding-usersjessib
there's no need for User#find_by_param. clean it up
2013-09-02document the logfile option in the defaults.ymlAzul
2013-09-02add config setting for logfileAzul
This is the most simple thing that could possibly work. If you do not specify a :logfile in your environments config Rails will use the default.
2013-08-30also replace find_by_param in billing engineAzul
2013-08-30there's no need for User#find_by_param. clean it upAzul
2013-08-27Not ideal way to do it, but was proving complicated to have a config file ↵jessib
specify which gems for which environments. Here, we have the billing gem included for the development and test environments only, hardcoded in the Gemfile. Then we show the links to billing based on a config file setting. The setting itself could be used to specify different types of billing, but isn't yet.
2013-08-27Merge branch 'master' into billing_with_testsjessib
2013-08-27Merge pull request #72 from azul/feature/token-based-authjessib
Feature: Token based auth
2013-08-27refactor: Changing the py test to use less globals and session only locally.Azul
2013-08-27use token to update user passwordAzul
2013-08-27separate different tests for showing non existant userAzul
This way the failed stubbing errors were more telling
2013-08-27token.user will get you the right userAzul
This way we can stub the token to return the user directly. Stubbing User.find_by_param is not a good idea as it will make all calls to User#find_by_param with a different id fail.
2013-08-27do not redirect if no token presentAzul
So far we allow two mechanisms of authentication: * session based * token based If token fails session will be atempted in most cases. So we can't just redirect here or we get a double render error.
2013-08-27make sure find_record still works with real recordsAzul
2013-08-27clear token on logout with testAzul
2013-08-27basic testing for token based auth in testsAzul
2013-08-27first steps towards enabling token based authAzul
2013-08-27sort authentication controller extensionAzul
2013-08-27minor: remove puts lineAzul
2013-08-26add public/img and config/couchdb.yml.* to gitignoreAzul
[ci skip]
2013-08-22Disable billing for pull request.jessib