oauth-oidc-misconfiguration

Tests OAuth and OIDC flows for redirect, state, PKCE, and token validation misconfigurations.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/lNwNl/Praxis --skill oauth-oidc-misconfiguration-lnwnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oauth-oidc-misconfiguration
Source: https://github.com/lNwNl/Praxis/tree/main/skills/_disabled/oauth-oidc-misconfiguration
Command: npx skills add https://github.com/lNwNl/Praxis --skill oauth-oidc-misconfiguration-lnwnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? OAuth 2.0 and OpenID Connect integrations frequently contain subtle misconfigurations in redirect URI validation, state and nonce handling, PKCE enforcement, and token audience checks that lead to account takeover or token theft, and this Skill provides a focused checklist for finding them. ## Core Features & Use Cases - Misconfiguration Checklist: Covers state handling, redirect_uri validation, PKCE enforcement, OIDC nonce validation, token audience and issuer checks, account binding, and scope handling. - Quick Triage Workflow: Guides mapping the full authorize/callback/token flow, replaying callbacks with altered parameters, and comparing SPA, mobile, and web clients for weaker validation. - Related Skill Routing: Links to JWT token attacks, CORS misconfiguration, SAML SSO assertion attacks, and CSRF skills for adjacent vulnerability classes. - Use Case: When testing an application that offers "Login with Google" or another identity provider, load this Skill to systematically replay callback flows with altered state, nonce, and redirect_uri values to find account binding or token reuse flaws. ## Quick Start Load this skill when the target uses OAuth or OIDC login and test the callback flow by replaying requests with modified state, nonce, and redirect_uri parameters.

Frequently Asked Questions about oauth-oidc-misconfiguration

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

FAQPage Schema
How do I test OAuth redirect_uri validation for vulnerabilities?▼

Replay the authorize and callback flows with altered redirect_uri values, checking for prefix matching, open redirect chaining, path confusion, and leftover localhost entries. Weak validation can let attackers steal authorization codes.

What OAuth misconfigurations lead to account takeover?▼

Missing or predictable state parameters, unenforced PKCE for public clients, unvalidated OIDC nonces, and weak account binding at the callback are common causes. These let attackers bind their identity to a victim session or intercept tokens.

Does this skill cover JWT token attacks?▼

It focuses on OAuth and OIDC flow misconfigurations rather than token cryptography. For JWT header abuse and token attacks, it cross-references a dedicated jwt-oauth-token-attacks skill.

When should I check PKCE enforcement during a pentest?▼

Check PKCE whenever public clients such as SPAs or mobile apps use the authorization code flow. Verify the code verifier is enforced and that the flow cannot be downgraded to a plain code exchange.

What are the limitations of this OAuth testing checklist?▼

It is a manual testing playbook without automated scripts, so results depend on the tester's execution. It also defers adjacent areas like SAML federation, CORS exposure, and CSRF to separate specialized skills.