TL;DR: Bearer tokens stay reusable by whoever presents them, which leaves stolen or logged tokens open to replay until expiry, according to WorkOS. API access needs cryptographic proof from the presenter when sensitive paths cannot rely on possession alone.
Editorial analysis by NHI Mgmt Group, based on content published by WorkOS: “Bearer tokens vs sender-constraining tokens: Why possession alone isn't enough”.
Key questions
Q: Why do sender-constraining tokens reduce replay risk?
A: They require the requester to prove control of a private key that matches the token binding.
Q: When should teams use DPoP instead of bearer tokens?
A: Use DPoP when the token crosses trust boundaries, the client can handle request signing, and replay would create meaningful business or security impact.
Q: What breaks when bearer tokens are stolen or logged?
A: Bearer tokens become immediately reusable because possession is enough to authorize the request.
Practitioner guidance
- Map bearer-token exposure paths Inventory where access tokens can leak through logs, browser storage, query strings, and third-party scripts, then classify which APIs can tolerate replay risk and which cannot.
- Require proof of possession for sensitive APIs Use sender-constraining for access paths that cross trust boundaries or carry regulated data, so token replay alone does not grant access.
- Choose DPoP for public clients Prefer DPoP when browser or mobile clients need sender-constrained access without changing the TLS stack, and reserve mTLS for environments that can sustain certificate operations.
Bottom line: Bearer-token designs keep authorization tied to possession, which means any leaked token can be reused until expiry unless other controls intervene.
Glossary terms: Bearer Token, Sender-Constraining Token, Proof-of-Possession, DPoP
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Bearer tokens are a replay problem, not just an authentication convenience: the model assumes the holder of the string is the legitimate caller. That assumption works only while token confidentiality is perfect, which is not a realistic governance premise in browser, logging, and multi-tenant environments. The practical conclusion is that token design must be assessed as a control boundary, not just an implementation detail.
A question worth separating out:
Q: How should teams decide between DPoP and mTLS?
A: Choose DPoP when you need sender-constraining with lower deployment friction and broader client compatibility. Choose mTLS when the environment can support certificate lifecycle management and you need stronger transport-layer binding, such as in regulated or high-assurance API deployments.
👉 Read our full editorial: Sender-constraining tokens close the bearer token theft gap