---
type: "raw_signal"
id: "announcing-dpop-support-for-google-oauth-securing-refresh-339ece"
slug: "announcing-dpop-support-for-google-oauth-securing-refresh-339ece"
title: "Announcing DPoP Support for Google OAuth: Securing Refresh Tokens"
description: "Google OAuth Platform has added support for DPoP (Demonstrating Proof-of-Possession) to sender-constrain refresh tokens."
retrieval_nugget: "Google OAuth Platform has added support for DPoP (Demonstrating Proof-of-Possession) to sender-constrain refresh tokens."
observed_at: "2026-10-16"
record_date: "2026-10-16"
date_kind: "observed_at"
why_it_matters: "Google OAuth Platform has added support for DPoP (Demonstrating Proof-of-Possession) to sender-constrain refresh tokens. Google says the cryptographic binding is intended to reduce the usefulness of stolen refresh tokens in infostealer and adversary-in-the-middle attacks. Access tokens remain short-lived Bearer tokens. The announcement also points to Google Cloud Secure Token Service (STS) for sec"
novelty: "notable"
verification_level: "source-linked"
signal_type: "release"
source_platform: "developers.googleblog.com"
topics: ["google"]
entities: ["Google","Google OAuth Platform","Google Cloud Secure Token Service","Model Context Protocol"]
related_patterns: ["agent-security-moves-to-runtime-boundaries"]
source_url: "https://developers.googleblog.com/announcing-dpop-support-for-google-oauth-securing-refresh-tokens"
source_urls: ["https://developers.googleblog.com/announcing-dpop-support-for-google-oauth-securing-refresh-tokens"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "signal:announcing-dpop-support-for-google-oauth-securing-refresh-339ece"
status: "published"
visuals: []
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/signals/announcing-dpop-support-for-google-oauth-securing-refresh-339ece/","markdown":"https://newruntime.com/signals/announcing-dpop-support-for-google-oauth-securing-refresh-339ece.md","json":"https://newruntime.com/signals/announcing-dpop-support-for-google-oauth-securing-refresh-339ece.json"}
---

# Announcing DPoP Support for Google OAuth: Securing Refresh Tokens

## Retrieval answer

Google OAuth Platform has added support for DPoP (Demonstrating Proof-of-Possession) to sender-constrain refresh tokens.

Google OAuth Platform has added support for DPoP (Demonstrating Proof-of-Possession) to sender-constrain refresh tokens. Google says the cryptographic binding is intended to reduce the usefulness of stolen refresh tokens in infostealer and adversary-in-the-middle attacks. Access tokens remain short-lived Bearer tokens. The announcement also points to Google Cloud Secure Token Service (STS) for secure token delegation across multi-agent and Model Context Protocol workloads. The change is an OAuth credential-protection capability for developers integrating with Google; the announcement does not establish adoption levels or measured reductions in attacks.

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: [Signals](https://newruntime.com/signals.json): Open the signals and the raw-signal archive.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)
