Back to catalog
Static reviewDevelopment

Skill dossier

configuring-oauth2-authorization-flow

Source declaration

Configures secure OAuth 2.0 authorization flows, including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token lifecycle management, and scope design per OAuth 2.1. Use when implementing or hardening OAuth 2.0 authentication/authorization for web, mobile, SPA, or machine-to-machine clients.

The author's original description, preserved in English. It describes intent, not verified performance.

Configures secure OAuth 2.0 authorization flows, including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token lifecycle management, and scope design per OAuth 2.1. Use when implementing or hardening OAuth 2.0 authentication/authorization for web, mobile, SPA, or machine-to-machine clients.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Configures secure OAuth 2.0 authorization flows, including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token lifecycle management, and scope design per OAuth 2.1. Use when implementing or hardening OAuth 2.0 authentication/authorization for web, mobile, SPA, or machine-to-machine clients. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/configuring-oauth2-authorization-flow/SKILL.md:L105]
  • Step 1: Authorization Code Flow with PKCE [Source statement; provisional, not tested. Evidence: skills/configuring-oauth2-authorization-flow/SKILL.md:L107]
  • Step 2: Scope Design [Source statement; provisional, not tested. Evidence: skills/configuring-oauth2-authorization-flow/SKILL.md:L119]
  • Step 3: Token Security [Source statement; provisional, not tested. Evidence: skills/configuring-oauth2-authorization-flow/SKILL.md:L125]
  • Step 4: Client Credentials Flow [Source statement; provisional, not tested. Evidence: skills/configuring-oauth2-authorization-flow/SKILL.md:L132]
  • Step 5: Security Hardening [Source statement; provisional, not tested. Evidence: skills/configuring-oauth2-authorization-flow/SKILL.md:L139]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/configuring-oauth2-authorization-flow/SKILL.md:L1-L55]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
54.8 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/configuring-oauth2-authorization-flow/assets/template.mdReference2.8 KB
skills/configuring-oauth2-authorization-flow/LICENSEOther11 KB
skills/configuring-oauth2-authorization-flow/references/api-reference.mdReference1.5 KB
skills/configuring-oauth2-authorization-flow/references/standards.mdReference2.2 KB
skills/configuring-oauth2-authorization-flow/references/workflows.mdReference5.3 KB
skills/configuring-oauth2-authorization-flow/scripts/agent.pyScript5.4 KB
skills/configuring-oauth2-authorization-flow/scripts/process.pyScript19.9 KB
skills/configuring-oauth2-authorization-flow/SKILL.mdInstruction6.7 KB

SKILL.md frontmatter

{
  "name": "configuring-oauth2-authorization-flow",
  "description": "Configures secure OAuth 2.0 authorization flows, including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token lifecycle management, and scope design per OAuth 2.1. Use when implementing or hardening OAuth 2.0 authentication/authorization for web, mobile, SPA, or machine-to-machine clients.",
  "domain": "cybersecurity",
  "subdomain": "identity-access-management",
  "tags": [
    "iam",
    "identity",
    "access-control",
    "authentication",
    "authorization",
    "oauth2",
    "oidc",
    "pkce"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.AA-01",
    "PR.AA-02",
    "PR.AA-05",
    "PR.AA-06"
  ],
  "mitre_attack": [
    "T1528",
    "T1550.001",
    "T1539",
    "T1606.001",
    "T1212"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "initial-access",
      "positioning"
    ],
    "techniques": [
      {
        "id": "T1550.001",
        "name": "Use Alternate Authentication Material: Application Access Token",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "F1004",
        "name": "Access with Stolen Session Cookie",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "F1006",
        "name": "Account Takeover",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "T1539",
        "name": "Steal Web Session Cookie",
        "tactic": "positioning",
        "source": "attack"
      }
    ]
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Objectives

    Source-described action candidate under “Objectives”; not verified execution.

  4. 04
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  5. 05
    Action

    Authorization Code + PKCE: Recommended for all client types (web, mobile, SPA). PKCE is mandatory in OAuth 2.1.

    Source-described action candidate under “OAuth 2.0 Grant Types”; not verified execution.

  6. 06
    Action

    Client Credentials: Machine-to-machine authentication without user context.

    Source-described action candidate under “OAuth 2.0 Grant Types”; not verified execution.

Inspect all extracted workflow candidates (52 candidate steps)
  1. 07
    Input

    Device Authorization Grant (RFC 8628): For input-constrained devices (smart TVs, CLI tools).

    Source-described input candidate under “OAuth 2.0 Grant Types”; not verified execution.

  2. 08
    Action

    Refresh Token: Long-lived token to obtain new access tokens without re-authentication.

    Source-described action candidate under “OAuth 2.0 Grant Types”; not verified execution.

  3. 09
    Action

    Client generates random `codeverifier` (43-128 characters, unreserved URI chars)

    Source-described action candidate under “PKCE (Proof Key for Code Exchange)”; not verified execution.

  4. 10
    Action

    Client computes `codechallenge = BASE64URL(SHA256(codeverifier))`

    Source-described action candidate under “PKCE (Proof Key for Code Exchange)”; not verified execution.

  5. 11
    Action

    Authorization request includes `codechallenge` and `codechallengemethod=S256`

    Source-described action candidate under “PKCE (Proof Key for Code Exchange)”; not verified execution.

  6. 12
    Action

    Token request includes original `codeverifier`

    Source-described action candidate under “PKCE (Proof Key for Code Exchange)”; not verified execution.

  7. 13
    Action

    Server validates `SHA256(codeverifier)` matches stored `codechallenge`

    Source-described action candidate under “PKCE (Proof Key for Code Exchange)”; not verified execution.

  8. 14
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  9. 15
    Action

    Step 1: Authorization Code Flow with PKCE

    Source-described action candidate under “Step 1: Authorization Code Flow with PKCE”; not verified execution.

  10. 16
    Action

    Generate cryptographically random codeverifier (min 43 chars)

    Source-described action candidate under “Step 1: Authorization Code Flow with PKCE”; not verified execution.

  11. 17
    Action

    Compute codechallenge using S256 method

    Source-described action candidate under “Step 1: Authorization Code Flow with PKCE”; not verified execution.

  12. 18
    Action

    Redirect user to authorization endpoint with parameters:

    Source-described action candidate under “Step 1: Authorization Code Flow with PKCE”; not verified execution.

  13. 19
    Action

    responsetype=code

    Source-described action candidate under “Step 1: Authorization Code Flow with PKCE”; not verified execution.

  14. 20
    Action

    clientid, redirecturi, scope, state

    Source-described action candidate under “Step 1: Authorization Code Flow with PKCE”; not verified execution.

  15. 21
    Action

    codechallenge, codechallengemethod=S256

    Source-described action candidate under “Step 1: Authorization Code Flow with PKCE”; not verified execution.

  16. 22
    Action

    User authenticates and consents

    Source-described action candidate under “Step 1: Authorization Code Flow with PKCE”; not verified execution.

  17. 23
    Action

    Authorization server redirects with authorization code

    Source-described action candidate under “Step 1: Authorization Code Flow with PKCE”; not verified execution.

  18. 24
    Action

    Exchange code + codeverifier for tokens at token endpoint

    Source-described action candidate under “Step 1: Authorization Code Flow with PKCE”; not verified execution.

  19. 25
    Action

    Validate state parameter matches original value

    Source-described action candidate under “Step 1: Authorization Code Flow with PKCE”; not verified execution.

  20. 26
    Action

    Step 2: Scope Design

    Source-described action candidate under “Step 2: Scope Design”; not verified execution.

  21. 27
    Input

    Define granular scopes: `read:users`, `write:orders`, `admin:settings`

    Source-described input candidate under “Step 2: Scope Design”; not verified execution.

  22. 28
    Action

    Follow least-privilege: request minimum scopes needed

    Source-described action candidate under “Step 2: Scope Design”; not verified execution.

  23. 29
    Action

    Implement scope validation on resource server

    Source-described action candidate under “Step 2: Scope Design”; not verified execution.

  24. 30
    Action

    Document scope hierarchy and consent requirements

    Source-described action candidate under “Step 2: Scope Design”; not verified execution.

  25. 31
    Action

    Step 3: Token Security

    Source-described action candidate under “Step 3: Token Security”; not verified execution.

  26. 32
    Action

    Store tokens securely (httpOnly cookies for web, keychain for mobile)

    Source-described action candidate under “Step 3: Token Security”; not verified execution.

  27. 33
    Action

    Implement token refresh with rotation (one-time-use refresh tokens)

    Source-described action candidate under “Step 3: Token Security”; not verified execution.

  28. 34
    Action

    Set appropriate expiration: access tokens 5-15 min, refresh tokens 8-24 hrs

    Source-described action candidate under “Step 3: Token Security”; not verified execution.

  29. 35
    Action

    Enable DPoP (Demonstration of Proof-of-Possession) for sender-constrained tokens

    Source-described action candidate under “Step 3: Token Security”; not verified execution.

  30. 36
    Action

    Implement token revocation endpoint

    Source-described action candidate under “Step 3: Token Security”; not verified execution.

  31. 37
    Action

    Step 4: Client Credentials Flow

    Source-described action candidate under “Step 4: Client Credentials Flow”; not verified execution.

  32. 38
    Action

    Register service client with clientid and clientsecret

    Source-described action candidate under “Step 4: Client Credentials Flow”; not verified execution.

  33. 39
    Action

    Request token: POST /oauth/token with granttype=clientcredentials

    Source-described action candidate under “Step 4: Client Credentials Flow”; not verified execution.

  34. 40
    Action

    Include scope for required permissions

    Source-described action candidate under “Step 4: Client Credentials Flow”; not verified execution.

  35. 41
    Action

    Store clientsecret securely (vault, env vars, not code)

    Source-described action candidate under “Step 4: Client Credentials Flow”; not verified execution.

  36. 42
    Action

    Implement certificate-based client authentication for higher assurance

    Source-described action candidate under “Step 4: Client Credentials Flow”; not verified execution.

  37. 43
    Action

    Step 5: Security Hardening

    Source-described action candidate under “Step 5: Security Hardening”; not verified execution.

  38. 44
    Action

    Enforce PKCE for all authorization code flows

    Source-described action candidate under “Step 5: Security Hardening”; not verified execution.

  39. 45
    Action

    Use exact redirect URI matching (no wildcards)

    Source-described action candidate under “Step 5: Security Hardening”; not verified execution.

  40. 46
    Action

    Implement CSRF protection with state parameter

    Source-described action candidate under “Step 5: Security Hardening”; not verified execution.

  41. 47
    Action

    Enable refresh token rotation and revocation on reuse detection

    Source-described action candidate under “Step 5: Security Hardening”; not verified execution.

  42. 48
    Action

    Apply RFC 9700 security best practices

    Source-described action candidate under “Step 5: Security Hardening”; not verified execution.

  43. 49
    Action

    Block implicit grant and ROPC (removed in OAuth 2.1)

    Source-described action candidate under “Step 5: Security Hardening”; not verified execution.

  44. 50
    Action

    Security Controls

    Source-described action candidate under “Security Controls”; not verified execution.

  45. 51
    Action

    Common Pitfalls

    Source-described action candidate under “Common Pitfalls”; not verified execution.

  46. 52
    Action

    Verification

    Source-described action candidate under “Verification”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

68 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

41 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 41 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

26 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 26 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/configuring-oauth2-authorization-flow/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/configuring-oauth2-authorization-flow/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/configuring-oauth2-authorization-flow
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.