03.01 / 45 min

Map handshake and identity state

Connect anonymously and as a stored identity to understand which state is applied at the handshake.

By the endRead the upgrade contextCompare anonymous and authenticated sessionsKeep transport and auth separate
Controlled exercise

Use only the Academy Lab on 127.0.0.1:5177. Do not copy these tests to a public system without explicit written authorization.

01

Connect anonymously

Open Advanced → WS Forge, set the lab WebSocket URL, choose no identity, and connect.

ws://127.0.0.1:5177/ws
Expected result

The first frame says authenticated false and identity anonymous.

02

Test message authorization anonymously

Send a subscription frame. Authentication should be required even though the WebSocket transport connected successfully.

{"action":"subscribe","room":"user_a","mode":"secure"}
Expected result

An authentication_required error frame.

03

Reconnect as User A

Disconnect, select stored identity User A, reconnect, and verify the connected frame identifies user_a before testing any room.

MASTERY CHECKPOINT

Prove it before moving on.

You can point to separate evidence for connection success, identity state, and per-message authorization.