Secure OAuth 2.0 and OpenID Connect implementations.
OAuth Hardening Specialist
OAuth 2.0, OpenID Connect, PKCE
Best for
- ▸Auditing OAuth 2.0 authorization code flows for redirect URI manipulation vulnerabilities
- ▸Implementing PKCE with S256 challenge method for single-page applications
- ▸Securing refresh token rotation with reuse detection in mobile apps
- ▸Validating JWT signature verification and preventing token leakage in API responses
What you'll get
- ▸Detailed vulnerability assessment with specific RFC violations, exploit scenarios, and step-by-step remediation with code snippets for secure token storage
- ▸Configuration checklist with exact redirect URI validation patterns, PKCE implementation code, and token lifecycle security controls
- ▸Security architecture review identifying attack vectors with specific fixes including CORS policies, state parameter validation, and sender-constrained tokens
Existing OAuth 2.0 or OpenID Connect implementation details including flow types, client configurations, redirect URIs, token handling code, and current security measures.
Specific security vulnerabilities identified with RFC-backed remediation steps, configuration changes, and code examples to implement proper OAuth security controls.
What's inside
“You are an OAuth Hardening Specialist. You identify and remediate OAuth 2.0 and OpenID Connect vulnerabilities in enterprise implementations, balancing security with operational feasibility. - **Protocol-First Analysis**: You map all findings to specific RFC violations (6749, 6819, 7636, 8705, 9449,...”
Covers
Not designed for ↓
- ×Basic authentication systems that don't use OAuth or OpenID Connect protocols
- ×General web application security beyond identity and authorization flows
- ×Setting up OAuth providers from scratch (focuses on hardening existing implementations)
- ×Non-OAuth SSO solutions like SAML or proprietary authentication systems
SupaScore
89.03▼
Evidence Policy
Standard: no explicit evidence policy.
Research Foundation: 8 sources (5 official docs, 1 books, 1 web, 1 academic)
This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.
Version History
v5.5 distilled from v2 via Claude Sonnet
Pipeline v4: rebuilt with 3 helper skills
Initial release
Works well with
Need more depth?
Specialist skills that go deeper in areas this skill touches.
Common Workflows
API Security Audit Pipeline
Comprehensive API security assessment starting with OAuth/OIDC hardening, followed by broader API security review and penetration testing validation
© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice