Back to Skills

oauth-oidc-misconfiguration

OAuth and OIDC misconfiguration testing playbook. Use when reviewing redirect URI handling, state and nonce validation, PKCE, token audience, callback binding, and identity-provider trust flaws.

1,281stars175forksUpdated 7/5/2026

Security Assessment

Safe(100/100)
Security Score100/100

About oauth-oidc-misconfiguration

A focused checklist for finding misconfigurations in OAuth 2.0 and OpenID Connect implementations. It targets the parts of the flow attackers most often abuse: redirect_uri validation (prefix matching, open-redirect chaining, path confusion, leftover localhost entries), state handling (missing, static, predictable, or not bound to a session), PKCE enforcement for public clients, OIDC nonce validation on returned ID tokens, token audience and issuer checks, cross-client token reuse, account-binding mistakes, and over-broad scope grants.

Load it when the target integrates identity providers such as Google, GitHub, Microsoft, or Okta, or when you observe parameters like authorize, callback, redirect_uri, code, state, nonce, or code_challenge, including mobile and SPA clients that may validate more weakly than the web flow. A quick-triage procedure maps the full flow (authorize, callback, token exchange, logout), replays callbacks with altered state, nonce, and redirect_uri, compares client types to find the weakest validation, and checks whether one provider account can be rebound to another local account.

The skill is a scoped checklist rather than an exhaustive cryptographic guide: for JWT header abuse and token-signature attacks it points to a companion jwt-oauth-token-attacks skill, and it cross-references related routes for CORS/cross-origin token exposure, SAML and enterprise SSO assertion attacks, and CSRF-driven login or binding bugs. It is best used during a web or API assessment to prioritize the highest-value authentication and authorization tests before diving into deeper token cryptanalysis.

FAQ

When should I load this skill?

When the app supports 'Login with' providers like Google, GitHub, Microsoft, or Okta, or you see OAuth/OIDC parameters such as authorize, callback, redirect_uri, code, state, nonce, or code_challenge.

What redirect_uri problems does it check for?

Weak validation such as prefix matching, open-redirect chaining, path confusion, and leftover localhost entries.

Does it cover JWT signature attacks?

No; for token cryptography and JWT header abuse it routes you to the separate jwt-oauth-token-attacks skill.

How does it suggest testing state and nonce?

Replay callback flows with altered state, nonce, and redirect_uri, and verify state is bound to the user session and the nonce is validated on the returned ID token.

Why compare SPA, mobile, and web clients?

Different client types can enforce validation such as PKCE more weakly, so comparing them surfaces the flow with the loosest checks.

Install oauth-oidc-misconfiguration

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill