AutoGineer
Generated banner for Dpop Adoption
Generated logo for Dpop Adoption

Dpop Adoption

GoogleOfficialPublished by Google

  • Skill
  • Tool integration
  • Security
  • Apache-2.0
  • Low risk
Download ZIP

From the author

Implement and debug OAuth 2.0 DPoP (RFC 9449) refresh token sender-constraining for WebCrypto, Node.js ES6, and browser runtimes integrating with Google's OAuth platform. Use when configuring non-extractable asymmetric key pairs (P-256), generating DPoP Proof JWTs for authorization code exchange and token refresh, or handling 400 use_dpop_nonce challenge retry loops at oauth2.googleapis.com/token. Don't use for unconstrained OAuth 2.0 flows (where refresh tokens are not bound to a client key pair), or for Google Cloud IAM / service account authentication.
— the description by Google

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides the architectural patterns and implementation requirements for integrating OAuth 2.0 Demonstrating Proof-of-Possession (DPoP) with Google's OAuth platform. It covers the cryptographic binding of refresh tokens to client-held private keys using WebCrypto, ensuring secure token exchange and refresh flows. The guide details mandatory security invariants, such as using non-extractable P-256 keys, proper DPoP Proof JWT construction, and handling nonce challenge retry loops, while emphasizing the necessity of a Backend-for-Frontend (BFF) pattern for secure browser-based integrations.

What it does

  • Generates non-extractable P-256 ECDSA key pairs for secure DPoP binding.
  • Constructs RFC 9449 compliant DPoP Proof JWTs with required claims.
  • Provides logic for handling 400 use_dpop_nonce challenge retry loops.
  • Defines mandatory export signatures for key management and proof generation.
  • Ensures compatibility across Node.js ES6 and browser WebCrypto runtimes.
  • Calculates cryptographic bindings for access tokens and authorization codes.

When to use it

  • When implementing sender-constrained OAuth 2.0 refresh tokens for Google APIs.
  • When building a Backend-for-Frontend (BFF) to secure SPA authentication.
  • When upgrading existing OAuth flows to meet DPoP security standards.
  • When debugging 400 Bad Request errors related to DPoP nonce challenges.
  • When needing to securely bind tokens to a client-side cryptographic boundary.

Advantages

  • Prevents token interception and replay attacks via cryptographic binding.
  • Leverages hardware-backed security through non-extractable key configuration.
  • Provides a standardized, RFC-compliant approach to sender-constraining.
  • Ensures robust error handling for nonce-based protocol challenges.
  • Promotes secure architecture by discouraging direct SPA-to-API token handling.

Usage examples

“How do I generate a non-extractable key pair for DPoP?”
The agent provides the generateDPoPKeyPair function using WebCrypto with extractable: false for the private key.
“Create a DPoP Proof JWT for a token refresh request.”
The agent generates a signed JWT with the correct header, htm, htu, iat, and jti claims as per the specified derivation rules.
“How should I handle a 400 use_dpop_nonce error from Google?”
The agent explains the retry logic: cache the new nonce, synthesize a new DPoP Proof JWT, and replay the request exactly once.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/google/dpop-adoption/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip dpop-adoption.zip -d .agents/skills

Documentation by Google

DPoP Adoption & Identity Security Architecture

Demonstrating Proof-of-Possession (DPoP, RFC 9449) secures OAuth 2.0 refresh tokens against interception and replay attacks by cryptographically binding them to a private key held exclusively by the client. In Google's OAuth 2.0 platform, DPoP binds the refresh token at the token endpoint, while access tokens issued for Google APIs are standard Bearer tokens (token_type: "Bearer").

1. Core Cryptographic & Architectural Invariants

When implementing DPoP helpers or upgrading HTTP clients, you MUST adhere to the following strict security invariants:

A. Universal WebCrypto & Runtime Compatibility

  • In modern ES6 JavaScript ("type": "module" for Node 18+ and browsers), ALWAYS access globalThis.crypto directly after verifying the environment context.

  • NEVER import legacy CommonJS modules via require('node:crypto') or reference browser-scoped window.crypto, as these cause module initialization crashes across hybrid runtimes.

B. Hardware-Backed Non-Extractable Key Persistence

  • Generate an Elliptic Curve key pair on the SECP256R1 (P-256) curve: { name: 'ECDSA', namedCurve: 'P-256' }.

  • CRITICAL SECURITY GUARDRAIL: The private key MUST be configured as non-extractable (extractable: false). This guarantees the private key can never leave the platform's cryptographic boundary (Secure Enclave, Android KeyStore, or JS sandbox memory), thwarting XSS and dependency token theft attacks.

  • Runtime Persistence Scope: In-memory WebCrypto (extractable: false) key generation applies to browser/IndexedDB contexts and single-process runtime harnesses; multi-instance or persistent server-side Node.js deployments should bind DPoP private keys via KMS/HSM/TPM so bound refresh tokens survive process restarts.

  • The public key MUST remain exportable (extractable: true) to allow emitting JSON Web Keys (JWKs).

C. Public JWK Formatting Standards

  • When exporting public keys to attach to DPoP Proof JWT headers, construct a clean JWK dictionary containing strictly:

    • "kty": "EC"

    • "crv": "P-256"

    • "x": Base64URL-encoded x-coordinate without trailing equal sign padding (=).

    • "y": Base64URL-encoded y-coordinate without trailing equal sign padding (=).

  • NEVER expose private key parameters ("d") or superfluous metadata.

D. IEEE P1363 vs. ASN.1 DER Signature Disambiguation

  • DPoP Proof JWTs require raw concatenated coordinate signatures ($R \parallel S$, exactly 64 bytes for P-256) per IEEE P1363 and RFC 7518.

  • WebCrypto Native Rule: In standard WebCrypto (crypto.subtle.sign), ECDSA signatures are ALREADY emitted natively in raw IEEE P1363 format (concatenated 32-byte r and s buffers, 64 bytes total). DO NOT attempt DER-to-Raw conversion on crypto.subtle.sign outputs, as parsing a 64-byte raw buffer as ASN.1 DER causes an immediate runtime exception (Invalid DER sequence). Directly base64url-encode the raw ArrayBuffer.

  • Legacy API Fallback: If and only if implementing in legacy Java/Android (java.security.Signature) or Node CommonJS (crypto.createSign), convert ASN.1 DER output to raw 64-byte IEEE P1363 format before base64url encoding.

E. SPA & Backend-for-Frontend (BFF) Architecture

  • Secretless SPAs Limitation: Pure client-side single-page applications (SPAs) without a backend cannot use DPoP directly with Google APIs due to client_secret requirements on server endpoints and browser CORS limitations on the DPoP-Nonce response header.

  • BFF Pattern: To secure SPAs with DPoP, route authorization and token refresh requests through a Backend-for-Frontend (BFF) server-side client. The BFF sets access_type=offline, binds refresh tokens server-side using DPoP, and maintains secure session cookies with the frontend.

2. Implementation Rules & Mandatory Public API

When creating new modules, your module MUST explicitly export all functions below to integrate cleanly with CI/CD verification harnesses and automated probers. When inspecting or refactoring existing codebases, ensure equivalent cryptographic and RFC 9449 logic is present. Obey strict claim derivation logic in all cases:

A. DPoP Proof JWT Claim Derivation Rules (createDPoPProof)

When generating the DPoP Proof JWT in createDPoPProof:

1. JOSE Header (typ, alg, jwk):

// Header
{
  "typ": "dpop+jwt",
  "alg": "ES256",
  "jwk": await exportPublicJWK(publicKey)
}

2. Payload Claims:

  • "htm": Uppercase HTTP Method ("POST" for token requests).

  • "htu": Target URI stripped of query parameters and hash fragments using sanitizeHTU(htu). For token requests, this is https://oauth2.googleapis.com/token.

  • "iat": Current integer epoch timestamp in seconds (Math.floor(Date.now() / 1000)).

  • "jti" (Critical Invariant):

    1. If an explicit jti argument is provided to createDPoPProof, use that exact string over all others.

    2. Otherwise, if an authCode argument is provided (during initial code exchange), set jti = await calculateAuthCodeJti(authCode) where calculateAuthCodeJti computes base64url(sha256(authCode)) to ensure the DPoP proof is cryptographically bound to the authorization code.

    3. Only if neither jti nor authCode is provided, generate a fresh cryptographic random string via generateRandomString() (such as crypto.getRandomValues(new Uint8Array(24)) base64url encoded).

  • "ath" (Optional): If an accessToken argument is provided for RFC 9449 resource requests, compute base64url(sha256(accessToken)) via calculateATH(accessToken) and inject it (RFC 9449 Section 6.1).

  • "nonce" (Optional): If a nonce argument is provided, inject it directly into the payload.

B. Explicit Export Signatures
// 1. Key generation & JWK export
export async function generateDPoPKeyPair() // -> { publicKey, privateKey } (private key extractable=false)
export async function exportPublicJWK(publicKey) // -> { kty: 'EC', crv: 'P-256', x, y }

// 2. Proof generation & validation
export async function createDPoPProof({ privateKey, publicKey, htm, htu, nonce, accessToken, authCode, jti }) // -> signed JWT string
export async function verifyDPoPProof(dpopProofJwt) // -> { isValid: boolean, header, payload, error }
export function sanitizeHTU(htu) // -> URL stripped of query and hash: const u = new URL(htu); return `${u.origin}${u.pathname}`;

// 3. Cryptographic & encoding utilities
export function base64UrlEncode(buffer) // -> Uint8Array/ArrayBuffer to base64url string without '=' padding
export function base64UrlDecode(str) // -> base64url string to Uint8Array/Buffer
export function stringToBase64Url(str) // -> UTF-8 string to base64url
export function base64UrlToString(str) // -> base64url to UTF-8 string
export function generateRandomString(byteLength = 32) // -> cryptographic random base64url string
export async function calculateATH(accessToken) // -> base64url(sha256(accessToken)) per RFC 9449 Sec 6.1
export async function calculateAuthCodeJti(code) // -> base64url(sha256(code))
export async function generatePKCE() // -> { codeVerifier (>=43 chars), codeChallenge, codeChallengeMethod: 'S256' }

3. Token Endpoint & Resource Request Workflow

When integrating with Google's OAuth 2.0 platform:

  1. Token Endpoint Requests (oauth2.googleapis.com/token):

    • Attach the DPoP Proof JWT in the DPoP HTTP header: `DPoP: ${proofJwt}` when making POST requests for code exchange (grant_type=authorization_code) and token refresh (grant_type=refresh_token).

  2. Resource API Requests:

    • Google's token endpoint returns "token_type": "Bearer". Downstream requests to Google APIs (e.g. Calendar, Drive, Gmail) use standard `Authorization: Bearer ${accessToken}` headers without DPoP headers.

  3. Single-Retry Nonce Challenge Loop & Workflow Isolation:

    • If Google's token endpoint returns HTTP 400 Bad Request with error: "use_dpop_nonce" and a "DPoP-Nonce" response header:

      • Workflow Isolation: Google's authorization server enforces workflow isolation between authorization code exchange and token refresh, returning an HTTP 400 use_dpop_nonce challenge to establish a fresh nonce namespace. This is standard RFC-compliant protocol behavior, not a server failure.

      • Cache the fresh nonce in client state (this.dpopNonce).

      • Immediately synthesize a new DPoP Proof JWT incorporating the updated nonce claim and a fresh jti.

      • Replay the failed token request exactly once. If the retried request fails, terminate immediately with an error to prevent infinite recursion.

4. Concise Agent Egress Protocol

When prompted to synthesize or output code deliverables under this skill, prioritize returning clean, directly importable code blocks without redundant conversational preambles or repetitive filler. For conceptual or architectural inquiries, provide standard direct answers.

5. References & Supporting Documentation

Developer Documentation (Google for Developers)
Developer Knowledge MCP Server

  • Agents equipped with Model Context Protocol (MCP) can query real-time Google Developer documentation using the Google Developer Knowledge MCP Server (npx -y @google/mcp-developer-knowledge-server) via developer_knowledge:search_documents and developer_knowledge:get_documents.

Standards & RFC Specifications

Files

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an MCP server, Needs Node.js

Security

What our scanner noticed· Low risk

  • Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Google
Publisher
Google (Official)
Source
google/skills · skills/identity/dpop-adoption · commit 2194d3b
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Google or Google.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download dpop-adoption.zip