An application can have multiple windows or scenes. Logging out in one must not leave sensitive content visible in another.
Evaluation approach
Manage sessions from a shared trusted source. Recheck authority and ownership as scenes become active.
Application example
After switching accounts in one window, another must not retain the old user's document. Vary background and return order.
Limits and considerations
Cleaning only the active screen does not cover multiple scenes.
Finding race conditions
Open a sensitive document in one scene while logging out or switching in another. Repeat with different completion orders. Check that already-loaded views stop displaying data even after the shared session object changes.
Checks and decisions
- Test scenes together
- Clear stale views
- Centralize authority
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.