leap_web.git/users, branch 0.2.7

Merge pull request #110 from azul/feature/cleanup-expired-tokens

2013-11-12T17:16:45+00:00

Feature/cleanup expired tokens

fix cornercase of non expiring tokens

2013-11-08T08:45:28+00:00

Token.destroy_all_expired to cleanup expired tokens (#4411)

2013-11-08T08:45:09+00:00

only check number of disabled identities to make test more robust

2013-11-07T11:46:28+00:00

use the account lifecycle from UsersController#destroy

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

destroy all tickets created by a user when account is destroyed

2013-11-06T10:30:33+00:00

In order to keep the users engine independent of the tickets engine i added a generic load hook to the account model. The tickets engine then monkeypatches the account destruction and destroys all tickets before the user is destroyed.

The tickets are destroyed first so that even if things break there should never be tickets with an outdated user id.

I would have prefered to use super over using an alias_method_chain but I have not been able to figure out a way to make account a superclass of the account extension and still refer to Account from the users engine.

integration test for blocking handles after account destroyed

2013-11-06T09:20:33+00:00

has not been run yet.

refactor: extract method on account test

2013-11-06T09:10:44+00:00

also test one can't login anymore after destroying the account.

Identity.destroy_all_disabled will clean up disabled identities

2013-11-05T16:03:55+00:00

This is mostly for cleaning up after tests so far. But we might expand this to destroy all identities disabled before a certain date.

disabled identities to block handles after a user was deleted

2013-11-05T11:15:08+00:00