competition-jwt-claim-confusionlisted

# Competition JWT Claim Confusion Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first. Use this skill when the decisive bug is not just "there is a JWT," but how headers, claims, and key selection turn into accepted identity. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Split the token path into parse, key lookup, signature or decryption, claim validation, and final acceptance. 2. Record header fields, claims, key source, issuer, audience, and role mapping before mutating anything. 3. Separate possession of a token from the exact service that accepts it. 4. Keep parser behavior, trust policy, and resulting app session or privilege in one chain. 5. Reproduce the smallest token-to-acceptance flow that proves the decisive confusion. ## Workflow ### 1. Map Header And Key Selection - Record header fields such as `alg`, `kid`, `typ`, `cty`, `jku`, or embedded key material when present. - Note where keys come from: static config, JWKS, local file, cache, or dynamic lookup. - Keep token parser, key selection path, and validation mode tied together. ### 2. Prove Claim-To-Privilege Acceptance - Show how subject, audience, issuer, tenant, scope, role, or custom claims become app session, route access, or backend privilege. - Rec