competition-oauth-oidc-chain

Trace OAuth and OIDC redirect flows to prove token-to-identity acceptance in CTF sandboxes.

7|4|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/dbx0/skills --skill competition-oauth-oidc-chain-dbx0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-oauth-oidc-chain
Source: https://github.com/dbx0/skills/tree/main/skills/identity-access/credential-access/competition-oauth-oidc-chain
Command: npx skills add https://github.com/dbx0/skills --skill competition-oauth-oidc-chain-dbx0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about competition-oauth-oidc-chain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace an OAuth redirect flow in a CTF challenge?

Map the chain in order: entry route, authorize request, redirect, callback parameters, token exchange, refresh, and the final accepting service. Record scopes, state, nonce, PKCE material, and redirect URIs before mutating anything.

How to prove a token becomes accepted identity in OIDC?

Show how the code, ID token, or access token turns into an app session, claims mapping, tenant selection, or granted privilege. Record token claims, audience, subject, expiration, and the exact backend edge that accepts them.

What is the difference between token possession and authorization?

Possessing a token only proves you hold it; authorization requires showing where the backend accepts its claims. This skill separates UI login success from backend authorization success to avoid false conclusions.

When should I use JWT claim analysis instead of OAuth chain tracing?

Use JWT claim analysis when the hard part is header parsing, claim normalization, key lookup, or token validation confusion after issuance. Use OAuth chain tracing when the challenge centers on redirects, callbacks, and token exchange.

Why does OAuth analysis fail when stopping at the callback?

Stopping at the callback misses the token exchange and claim acceptance steps that prove the actual identity edge. You must link browser-side redirect evidence with backend-side token acceptance to complete the proof.