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.
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.