Exercise 09 teaching plan
Teach server-side logout revocation as one example of OWASP A07 Authentication Failures. Students should explain why a retained token works after the unsafe logout, repair the policy, and demonstrate rejection without breaking fresh logins or independent sessions.
Preparation
Use Node.js 22+, a browser, and an editor. No packages or external services are required. Follow the student-kit README from a fresh export and test the actual learner machine environment. Run starter and solution checks: expected counts are 8/10 and 10/10. Use only fictional credentials and loopback. See walkthrough and rubric.
Session outline
| Activity | Minutes | Evidence |
|---|---|---|
| Open supplied app and check setup | 10 | Successful local login/profile |
| Capture, logout, replay | 10 | Starter still grants access |
| Explain session state | 10 | Client/server distinction |
| Make the guided policy repair | 15 | One-function change |
| Restart, create fresh token, verify | 10 | Replay rejected, fresh login works |
| Independent sessions and checks | 10–15 | Other tab works, 10/10 checks |
| Explain and submit | 10 | Completed evidence table |
Allow 75–90 minutes after setup, including troubleshooting. No prior lesson or backend expertise is assumed; explain import, function calls, arguments and return before asking learners to edit.
Teaching emphasis
The central distinction is “the screen no longer has a credential” versus “the server no longer accepts that credential.” Replay uses the same protected endpoint as normal access. Keep the capture/logout/replay sequence in one server lifetime: restarting alone can create a misleading success.
Use two tabs signed in independently to show per-session logout. State explicitly that global sign-out, cookies, TLS, MFA, session fixation prevention and rate limiting are separate topics. The app's memory-only bearer tokens and published fictional credentials are local teaching mechanisms.
Assessment and support
Grade the reasoning and evidence using the 20-point rubric. Do not accept a screenshot of a signed-out label as proof. Give partial credit for a correct explanation even if setup problems prevent a complete run, according to your course policy; do not invent passed checks. A correct repair cannot simply deny every request or clear every session.