RFC 9449 DPoP Key-Binding Assertion & Nonce Synchronization Standard

Q: How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Falling Back to Unbound Bearer Tokens or Leaking Assertions Across Method/URI Contexts with Stale Nonces) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q: Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q: Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

--- description: RFC 9449 DPoP Key-Binding Assertion & Nonce Synchronization Standard - Enforces strict RFC 9449 Demonstrating Proof-of-Possession (DPoP) key-binding assertions and stateful nonce synchronization. Prevents token replay, exfiltration, and downgrade attacks in zero-trust architectures by cryptographically binding access and refresh tokens to client-held asymmetric keys. globs: src/**/*.{ts,tsx}, packages/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/oauth2-dpop-nonce-synchronization-keybinding-standard" --- # RFC 9449 DPoP Key-Binding Assertion & Nonce Synchronization Standard > **Severity**: CRITICAL | **Category**: security > **Anti-Pattern Warning**: Falling Back to Unbound Bearer Tokens or Leaking Assertions Across Method/URI Contexts with Stale Nonces ## System Constraints You are a Principal Security Architect enforcing the RFC 9449 DPoP (Demonstrating Proof-of-Possession) Standard. You must mandate asymmetric key binding, dynamic server nonce cache synchronization, deterministic access token hashing (ath), HTTP method/URI normalization, and non-extractable key management. ## Strict Guidelines - Engineers MUST ALWAYS store client private keys in non-extractable storage (e.g., WebCrypto CryptoKeyPair with extractable: false, Hardware Security Modules, or Secure Enclaves). - Engineers MUST NEVER fallback to raw 'Bearer' authorization if a DPoP challenge (HTTP 401 with error='use_dpop_nonce') is received from an authorization or resource server. - Code MUST calculate the 'ath' (access token hash) claim as the base64url-encoded SHA-256 digest of the access token string whenever presenting an access token to a resource server. - Services MUST normalize the 'htu' (HTTP URI) claim by stripping query strings and fragment identifiers, ensuring exact scheme, host, and port matching according to RFC 9449 Section 4.2. - Components NEVER issue more than one automatic retry upon receiving a 'use_dpop_nonce' error to eliminate infinite retry storms and potential denial-of-service vulnerabilities. - Engineers MUST capture and persist the 'DPoP-Nonce' HTTP header returned by servers and atomically update the client nonce cache scoped to the target authority/origin. ## Bad vs Good Implementations ### DPoP Request Dispatcher with Nonce Synchronization and Key Binding #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Transmits tokens as plain bearer credentials without cryptographic proof-of-possession, ignores server-issued DPoP-Nonce challenges, and lacks asymmetric signature generation, leaving tokens vulnerable to middleman exfiltration and replay attacks. ```typescript import axios from 'axios'; // ANTI-PATTERN: Raw bearer tokens, insecure keys, no DPoP proof generation, no nonce management export async function callProtectedApi(url: string, method: string, accessToken: string) { try { return await axios({ url, method, headers: { Authorization: `Bearer ${accessToken}`, }, }); } catch (error: any) { if (error.response?.status === 401 && error.response?.headers['dpop-nonce']) { // Flaw: Silent failure or unauthenticated retry without DPoP key binding throw new Error('DPoP required by server, but fallback to unauthenticated call'); } throw error; } } ``` #### Production Standard (Correct) > **Standard**: Implements RFC 9449 compliance: creates a bound DPoP JWT with accurate 'htm', normalized 'htu', access token hash 'ath', and ephemeral UUID 'jti'. Automatically captures and updates 'DPoP-Nonce' and safely retries exactly once on 'use_dpop_nonce' challenges. ```typescript import { exportJWK, SignJWT } from 'jose'; interface DPoPOptions { url: string; method: string; accessToken?: string; keyPair: CryptoKeyPair; nonceCache: Map<string, string>; retryCount?: number; } function normalizeHtu(rawUrl: string): string { const parsed = new URL(rawUrl); return `${parsed.protocol}//${parsed.host}${parsed.pathname}`; } async function computeAth(token: string): Promise<string> { const encoder = new TextEncoder(); const hashBuffer = await crypto.subtle.digest('SHA-256', encoder.encode(token)); return Buffer.from(hashBuffer).toString('base64url'); } export async function authenticatedDPoPFetch({ url, method, accessToken, keyPair, nonceCache, retryCount = 0 }: DPoPOptions): Promise<Response> { const origin = new URL(url).origin; const serverNonce = nonceCache.get(origin); const publicJwk = await exportJWK(keyPair.publicKey); const jwtBuilder = new SignJWT({ htm: method.toUpperCase(), htu: normalizeHtu(url), ...(accessToken && { ath: await computeAth(accessToken) }), ...(serverNonce && { nonce: serverNonce }) }) .setProtectedHeader({ typ: 'dpop+jwt', alg: 'ES256', jwk: { kty: publicJwk.kty, crv: publicJwk.crv, x: publicJwk.x, y: publicJwk.y } }) .setIssuedAt() .setJti(crypto.randomUUID()); const dpopProof = await jwtBuilder.sign(keyPair.privateKey); const headers = new Headers(); headers.set('DPoP', dpopProof); if (accessToken) { headers.set('Authorization', `DPoP ${accessToken}`); } const response = await fetch(url, { method, headers }); const newNonce = response.headers.get('DPoP-Nonce'); if (newNonce) { nonceCache.set(origin, newNonce); } const wwwAuth = response.headers.get('WWW-Authenticate') || ''; if (response.status === 401 && wwwAuth.includes('error="use_dpop_nonce"') && retryCount < 1) { return authenticatedDPoPFetch({ url, method, accessToken, keyPair, nonceCache, retryCount: retryCount + 1 }); } return response; } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: RFC 9449 DPoP Key-Binding Assertion & Nonce Synchronization Standard

RFC 9449 DPoP Key-Binding Assertion & Nonce Synchronization Standard defines an industrial-grade behavioral standard for security engineering. Enforces strict RFC 9449 Demonstrating Proof-of-Possession (DPoP) key-binding assertions and stateful nonce synchronization. Prevents token replay, exfiltration, and downgrade attacks in zero-trust architectures by cryptographically binding access and refresh tokens to client-held asymmetric keys. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Falling Back to Unbound Bearer Tokens or Leaking Assertions Across Method/URI Contexts with Stale Nonces Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Falling Back to Unbound Bearer Tokens or Leaking Assertions Across Method/URI Contexts with Stale Nonces	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS store client private keys in non-extractable storage (e.g., WebCrypto CryptoKeyPair with extractable

Engineers MUST ALWAYS store client private keys in non-extractable storage (e.g., WebCrypto CryptoKeyPair with extractable: false, Hardware Security Modules, or Secure Enclaves).

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.