What problem does it solve? CTF challenges involving OAuth and OIDC often hide the decisive flaw in long redirect chains, token exchanges, and claim mapping, making it hard to prove exactly how a token becomes accepted identity or privilege. ## Core Features & Use Cases - Redirect Chain Mapping: Records entry routes, authorize parameters, callback values, token endpoints, and refresh paths in one compact chain. - Token-to-Identity Proof: Distinguishes token possession from actual backend acceptance by documenting claims, scopes, audience, and the accepting service edge. - Minimal Replayable Flow: Compresses findings into the smallest redirect-to-acceptance sequence with one canonical flow and one mutated variant. - Use Case: During a CTF web challenge, trace an OAuth login from the authorize redirect through the callback and token exchange to show exactly which claim or parameter mutation grants unauthorized access. ## Quick Start Ask the assistant to trace the OAuth redirect chain of the challenge login flow and prove where the token becomes accepted identity, after the ctf-sandbox-orchestrator has established sandbox assumptions.