Google adopts DPoP to protect OAuth 2.0 tokens from theft
Google's OAuth platform now supports Demonstrating Proof-of-Possession (DPoP), which cryptographically binds tokens to a client-generated key pair so stolen tokens cannot be replayed without the private key. DPoP applies only to refresh tokens, while shorter-lived access tokens remain standard Bearer tokens.
- DPoP binds tokens to a client-side asymmetric key pair
- Protection covers only Google OAuth refresh tokens
- Google and WICG are developing DBSC for session cookies
- Google Cloud STS is recommended for multi-agent delegation
Read next
Security