Protego field desk

Chapter 3 · Identity and Access

5. Recognize Authentication

Trace the relationship between identity verification, a session, and signing out.

Video transcript

Casey signs in. How does the app remember Casey? Authentication checks identity. A session can carry the result of a successful sign-in across later requests to the application. Casey provides sign-in proof. The service verifies it before it treats Casey as signed in. The service records a session and can send a session cookie to Casey's browser. The browser sends that cookie on a later request. The app checks that the session is valid. The app can associate the request with Casey's identity. A protected page should require Casey to sign in again. First, the app verifies the user's proof. Later, it verifies that the session still applies. When Casey signs out, the app ends the session. Authentication identifies the user. Try the knowledge check before moving on to what that user can do.

Course outlineLesson 5 of 8
Ethical Hacking for Beginners: course overview

Lesson notes

Authentication checks identity. In the practice app, a sign-in service verifies Casey’s proof and creates a session after successful sign-in.

The app can send the browser a cookie that associates later requests with that session. The server checks whether the session is valid before using Casey’s identity.

Sign-out should end that session. A protected page should then require Casey to sign in again.

Try it

Make a three-row table for a protected page before sign-in, after sign-in, and after sign-out. Write whether the app should recognize an active session at each step.

OWASP ASVS Session Management
Knowledge Check

1. Which step establishes Casey’s identity?

2. Why can the app recognize Casey on another request?

3. What should happen if Casey opens a protected page after signing out?