leap_web.git/users/app/controllers, branch 0.2.7

use the account lifecycle from UsersController#destroy

2013-11-06T10:55:43+00:00

notify user their account was successfully deleted (refs #4216)

2013-10-30T19:17:43+00:00

Also fixes a cornercase when admins deleted their own account. So far they would be redirected to the users list - which then refused access. Now they'll be redirected to the home landing page as well.

use token auth when accessing the api from webapp

2013-09-24T08:48:32+00:00

One failing integration test still needs to be fixed

user.account shortcut to Account.new(user)

2013-09-18T08:27:19+00:00

Merge pull request #73 from azul/bugfix/3623-teardown-test-data-properly

2013-09-03T17:48:13+00:00

Bugfix/3623 teardown test data properly

Merge pull request #75 from azul/feature/token-expiry

2013-09-03T17:43:34+00:00

Token expiry

clearify usage of V1::UsersController#index for autocomplete

2013-09-03T09:08:55+00:00

[skip ci]

remove email aliases controller - we don't use it anymore

2013-09-03T08:50:00+00:00

Cleanup sessions controller - webapp logs in through the api.

2013-09-03T08:49:00+00:00

So the #create and #update actions were not needed anymore. Also removed the tests

Account: Composition to handle User and its identities

2013-09-03T06:54:25+00:00

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).