Concept notes
Why this decision matters
OAuth Code Flow Debugger is focused practice for OAuth Authorization Code flow. It explains why each answer is safe, risky, or production-ready.
Debug the complete flow as a chain of bindings rather than a single login callback.
Learning objectives
- Bind callbacks with state.
- Preserve the PKCE verifier.
- Keep long-lived credentials out of browser JavaScript.
How to play
- Follow each redirect and token hop.
- Choose the control that restores the trust boundary.
- Review why valid-looking values can still belong to the wrong flow.
Scoring
- Correct flow repairs add 250 points.
- Misses enter local review.
- A perfect run scores 1,000.
Backend concept notes
Authorization Code flow separates browser redirects from server token exchange.
State, PKCE, and exact redirect matching address different substitution threats.
Common mistakes
- Accepting mismatched state.
- Generating a new PKCE verifier after redirect.
- Exposing refresh tokens to browser storage.
Review misses from this game
Related Backend Study Lab articles
Use the main site for deeper reading after playing.
Start here
Related Backend Study Lab tools
Use tools from the main site when you want to inspect real inputs.
FAQ
Short answers for how this game fits backend interview and study practice.
Is state replaced by PKCE?
No. They protect different bindings and are commonly used together.
Why must redirect URIs match exactly?
Exact matching prevents authorization codes from being redirected to attacker-controlled destinations.