Raw signalOct 16, 20261 min read1 source

Announcing DPoP Support for Google OAuth: Securing Refresh Tokens

In one minute

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.

Evidence / sources

  1. 1developers.googleblog.com/announcing-dpop-support-for-google-oauth-securing-refresh-tokens
All Signals

Next reads

Read next

Open the graph
  1. 01topicGoogleExplore the google topic hub.
  2. 02archiveSignalsOpen the signals and the raw-signal archive.
  3. 03sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract