Exercise 09 submission
Name or course identifier:
Environment and original observation
- Node version, browser, and whether you used repository or student kit:
- Before-repair normal profile request result and HTTP status before logout:
- Before-repair logout result:
- Before-repair normal profile request result and HTTP status after logout, without the retained token:
- Before-repair retained-token replay result and HTTP status:
- Why the signed-out screen was insufficient:
Record both normal requests and the retained-token replay separately. Do not paste token values or real credentials.
Repair
Paste your changed session-policy.mjs and explain which server-side state it changes. Why does revocation belong on the server? Why should logout leave other sessions intact?
Verification evidence
Confirm that you restarted after editing, then logged in and captured a new token. Confirm there was no restart between capture, logout, and replay.
| Scenario | Actual HTTP result or observation | What it demonstrates |
|---|---|---|
| Valid login and profile before logout | ||
| Retained token replay after logout | ||
| Fresh login and profile after logout | ||
| Other independently signed-in tab after first tab logs out |
Attach your own screenshots or response evidence without token strings. Paste the actual node checks.mjs output and report any failures.
Explanation
Explain client token clearing versus server revocation. Why would replaying a token from before a server restart be inadequate proof? What is the difference between logout and expiry? Name one authentication concern this focused lesson does not solve.