U4-2678 - Fix logging out and then logging in as another user, the sections, etc... do not get updated.

Created by Shannon Deminick 21 Aug 2013, 03:00:30 Updated by Shannon Deminick 01 Oct 2013, 03:23:13

we should look into the difference between a timeout caused logout and a "hard" logout, where the "hard" logout clears data when you leave the app and the soft one only clears it, if a different user logs in then the original one

Comments

Shannon Deminick 30 Sep 2013, 10:10:59

This is all done.

  • Works based on events broadcast from the root which is all handled in the userService
  • This ensures that only one request executes when first load instead of 3 (well i think the dashboard still makes an attempt but we can fix that)
  • Once the user is auth'd then the main/nav controllers do their thing.
  • If a user times out or logs out the mainController ensures that the user is cleared
  • If the same user logs back in, we detect its the same user and leave the cached tree and section data
  • If a new user logs in, we detect that and clear the tree and section caches and force them to reload


Priority: Normal

Type: Bug

State: Fixed

Assignee: Shannon Deminick

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version: 7.0.0

Sprint:

Story Points:

Cycle: