leap_web.git/users/app, branch 0.2.7 [leap_web] Merge pull request #110 from azul/feature/cleanup-expired-tokens 2013-11-12T17:16:45+00:00 jessib jessib@riseup.net 2013-11-12T17:16:45+00:00 8295db1a8cf334ff8666e5ec29455c199c7ffc73 Feature/cleanup expired tokens 
Feature/cleanup expired tokens
 fix cornercase of non expiring tokens 2013-11-08T08:45:28+00:00 Azul azul@leap.se 2013-11-07T22:36:37+00:00 a7cd2ef0877e79302f27fb175384a0cf4ded52d9 






Token.destroy_all_expired to cleanup expired tokens (#4411)
2013-11-08T08:45:09+00:00

Azul
azul@leap.se

2013-11-07T22:27:27+00:00

e2c0962077cf759b23639276cca42606ea2135ec












use the account lifecycle from UsersController#destroy
2013-11-06T10:55:43+00:00

Azul
azul@leap.se

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

ded302ebc6a9e145775f7847c5e89f91d683c777












destroy all tickets created by a user when account is destroyed
2013-11-06T10:30:33+00:00

Azul
azul@leap.se

2013-11-06T10:26:46+00:00

24598b5c5e4df20c423ec74ea8e9df1592483c6b

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.





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.







Identity.destroy_all_disabled will clean up disabled identities
2013-11-05T16:03:55+00:00

Azul
azul@leap.se

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

4a2490cc5eac1803be80fade65bbe9d32fa0bd9b

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





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

Azul
azul@leap.se

2013-11-05T11:12:13+00:00

99ecdbf71632970d4c83f99beea325e5d213e4c6












refactor: Identity.disable_all_for(user) on user destruction
2013-11-05T10:40:25+00:00

Azul
azul@leap.se

2013-11-05T10:40:25+00:00

b4ca13257341792f5e6496264c421af1888bcdb8

This way the identity model defines how identities should be disabled. We currently still destroy them. But it will be easy and nicely isolated to change this next.





This way the identity model defines how identities should be disabled. We currently still destroy them. But it will be easy and nicely isolated to change this next.







notify user their account was successfully deleted (refs #4216)
2013-10-30T19:17:43+00:00

Azul
azul@leap.se

2013-10-28T11:47:46+00:00

dd88c7f84cb3c497c6327c364b3c08993c51a08f

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.





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.







Fix button to enable account: https://leap.se/code/issues/4246
2013-10-28T20:10:12+00:00

jessib
jessib@riseup.net

2013-10-28T20:10:12+00:00

7aaedeaf6fdd2d84ebab7bde2f6a6bdcf8d930b8