Multiple accounts require explicit ownership of caches, keys and tasks. Changing the displayed username is insufficient.
Evaluation approach
Bind stored objects and operations to accounts. Avoid common storage for sensitive user data without isolation.
Application example
A download finishing during a switch must remain in its original account space or be canceled.
Limits and considerations
Mismatched tokens and caches can silently disclose another account's data.
What belongs in cache keys?
Object identifiers alone may collide across accounts. Include account and data context, then verify that logout removes the intended records.
Checks and decisions
- Use account-scoped keys
- Bind tasks
- Test switching races
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.