Identity & access

DPoP

Demonstrating Proof of Possession

An OAuth mechanism (RFC 9449) binding tokens to a client key pair, so a stolen access token cannot be replayed without the key.

With DPoP the client generates a key pair and, on every request, sends a DPoP header containing a JWT signed with the private key. It includes htm (HTTP method), htu (URL), iat, a unique jti and, for resource requests, ath (hash of the access token). The authorisation server binds issued tokens to the key's thumbprint via the cnf.jkt claim and the API checks the proof matches.

It brings sender-constrained tokens to browsers and mobile apps, where mTLS client certificates are impractical. A token exfiltrated by XSS or a log leak is useless without the private key, which can be a non-extractable WebCrypto key.

Servers must keep a replay cache of jti values within the acceptance window, or use server-provided nonces. It does not help if the attacker can run code in the client and ask it to sign proofs.

Request with a DPoP-bound tokenhttp
GET /v1/accounts HTTP/1.1
Host: api.example.com
Authorization: DPoP eyJhbGciOiJFUzI1NiIsImtpZCI6...
DPoP: eyJ0eXAiOiJkcG9wK2p3dCIsImFsZyI6IkVTMjU2IiwiandrIjp7...

Learn it properly

Compared

Also used in

Related terms