---
type: "post"
id: "announcing-dpop-support-for-google-oauth-securing-refresh-0a4963"
slug: "announcing-dpop-support-for-google-oauth-securing-refresh-0a4963"
title: "Announcing DPoP Support for Google OAuth: Securing Refresh Tokens"
description: "Google OAuth now supports DPoP for refresh-token protection."
retrieval_nugget: "Google OAuth now supports DPoP for refresh-token protection."
published_at: "2026-10-16"
updated_at: "2026-10-16"
record_date: "2026-10-16"
date_kind: "published_at"
topics: ["google"]
source_urls: ["https://developers.googleblog.com/announcing-dpop-support-for-google-oauth-securing-refresh-tokens"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:announcing-dpop-support-for-google-oauth-securing-refresh-0a4963"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:dfde68c1825d23a50017b378d4504c95ef94875242f365fac8e58c8623b3ee50","reviewed_at":"2026-10-16T04:04:01.495Z","source_evidence_count":1,"verified_claim_count":3,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":3,"implication_count":2,"watch_condition_count":1,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Credential security for connected agents depends partly on constraining how reusable tokens can be replayed, not only on what an agent is instructed to do.","observed_facts":[{"text":"Google OAuth Platform now supports DPoP to sender-constrain refresh tokens.","source_urls":["https://developers.googleblog.com/announcing-dpop-support-for-google-oauth-securing-refresh-tokens"]},{"text":"The announcement says short-lived access tokens remain standard Bearer tokens.","source_urls":["https://developers.googleblog.com/announcing-dpop-support-for-google-oauth-securing-refresh-tokens"]},{"text":"Google points to STS for secure token delegation across multi-agent and MCP workloads.","source_urls":["https://developers.googleblog.com/announcing-dpop-support-for-google-oauth-securing-refresh-tokens"]}],"mechanism":"DPoP binds refresh tokens to a cryptographic key, making a copied token alone less useful for replay while leaving access tokens as Bearer tokens.","why_now":"Google OAuth Platform has announced support, giving developers using its OAuth surface a concrete option as agent and MCP integrations require delegated credentials.","implications":["Teams can evaluate DPoP to reduce refresh-token replay exposure in Google OAuth integrations.","Delegated agent workflows still require careful assessment of access-token handling and end-to-end implementation."],"evidence_boundary":"The announcement describes the feature and intended threat mitigation, but supplies no adoption figures, independent validation, or measured reduction in compromises.","watch_conditions":["Watch for implementation guidance, client-library support, and evidence about how DPoP behaves across real delegated agent workflows."],"related_records":[],"new_branch_reason":"No prior New Runtime record was supplied for this specific Google OAuth DPoP release, so it starts a separate analytical record on token replay protection in agent integrations."}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/announcing-dpop-support-for-google-oauth-securing-refresh-0a4963/","markdown":"https://newruntime.com/posts/announcing-dpop-support-for-google-oauth-securing-refresh-0a4963.md","json":"https://newruntime.com/posts/announcing-dpop-support-for-google-oauth-securing-refresh-0a4963.json"}
---

# Announcing DPoP Support for Google OAuth: Securing Refresh Tokens

## Retrieval answer

Google OAuth now supports DPoP for refresh-token protection.

Google OAuth now supports DPoP for refresh-token protection. The platform binds long-lived refresh tokens cryptographically to a key, while short-lived access tokens remain standard Bearer tokens. Google says the design addresses infostealer malware and adversary-in-the-middle attacks. It also points developers to Google Cloud Secure Token Service (STS) for token delegation across multi-agent and Model Context Protocol workloads.

Thesis: Credential security for connected agents depends partly on constraining how reusable tokens can be replayed, not only on what an agent is instructed to do. Mechanism: DPoP binds refresh tokens to a cryptographic key, making a copied token alone less useful for replay while leaving access tokens as Bearer tokens. Why now: Google OAuth Platform has announced support, giving developers using its OAuth surface a concrete option as agent and MCP integrations require delegated credentials.

Implication: Teams can evaluate DPoP to reduce refresh-token replay exposure in Google OAuth integrations. Evidence boundary: The announcement describes the feature and intended threat mitigation, but supplies no adoption figures, independent validation, or measured reduction in compromises. Watch condition: Watch for implementation guidance, client-library support, and evidence about how DPoP behaves across real delegated agent workflows. These details matter because refresh-token protection does not by itself establish the security of an entire delegated workflow.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Google](https://newruntime.com/topics/google.md): Explore the google topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)