oauth-flow-test-authorlisted
Install: claude install-skill testland/qa
# oauth-flow-test-author
## Overview
OAuth 2.0 (RFC 6749) defines four grant types per [datatracker.ietf.org/doc/html/rfc6749][rfc6749]:
[rfc6749]: https://datatracker.ietf.org/doc/html/rfc6749
> "1. **Authorization Code** (§1.3.1): The authorization code is
> obtained by using an authorization server as an intermediary
> between the client and resource owner.
> 2. **Implicit** (§1.3.2): The implicit grant is a simplified
> authorization code flow optimized for clients implemented in a
> browser using a scripting language such as JavaScript.
> 3. **Resource Owner Password Credentials** (§1.3.3): The resource
> owner password credentials (i.e., username and password) can
> be used directly as an authorization grant to obtain an access
> token.
> 4. **Client Credentials** (§1.3.4): The client credentials can be
> used as an authorization grant when the authorization scope is
> limited to protected resources under the control of the
> client."
**Per RFC 9700 (OAuth 2.0 Security Best Current Practice, March 2025):**
- Implicit grant is **deprecated**.
- Resource Owner Password Credentials grant is **deprecated**.
- Authorization Code with PKCE (per [datatracker.ietf.org/doc/html/rfc7636][rfc7636])
is the canonical flow for **all** clients, public or confidential.
[rfc7636]: https://datatracker.ietf.org/doc/html/rfc7636
This skill is the per-flow test recipe. The canonical authorization-code +
PKCE flow is authored end to end in the Worked ex