# DPoP - does it really change anything?

**URL:** <https://community.auth0.com/t/dpop-does-it-really-change-anything/78476>\
**Category:** Get Help\
**Tags:** jwt\
**Created:** [February 17, 2022, 12:10pm UTC](https://community.auth0.com/t/dpop-does-it-really-change-anything/78476 "2022-02-17T12:10:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mnj](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/mnj/32/35292_2.png) [@mnj](https://community.auth0.com/u/mnj)\
**Post date:** [February 17, 2022, 12:10pm UTC](https://community.auth0.com/t/dpop-does-it-really-change-anything/78476/1 "2022-02-17T12:10:38Z")

</div>

I’ve been reading [Identity, Unlocked... Explained | Episode 1](https://community.auth0.com/t/identity-unlocked-explained-episode-1/49866).  
The problem statement was that access tokens, when stolen, can be used by an attacker freely (within the validity time of the token).  
To prevent that, one of the solutions is to use a DPoP proof - another JWT that would be sent to the Resource Server together with an access token to prove that the caller is the right entity.

However, I don’t understand how it fixes the initial problem. Initially, we were worried what happens if someone steals an access token. Now, didn’t we just change the problem into “what happens if someone steals a pair of access token and dpop proof”?

As I understand it, if I somehow possess someone’s pair of access token and dpop, I can use it freely.

---

<div class="post-metadata">

**Author:** ![Vittorio](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/vittorio/32/13432_2.png) [@Vittorio](https://community.auth0.com/u/Vittorio)\
**Post date:** [February 25, 2022, 11:49pm UTC](https://community.auth0.com/t/dpop-does-it-really-change-anything/78476/2 "2022-02-25T23:49:16Z")

</div>

Hi there! Capturing AT and DPOP proof only allows repeating the exact same call, as soon as HTTP method and URI change (as it is common in REST API) the DPOP proof is no longer usable and cannot be replayed. Compare this with classic bearer use of an AT, where holding the AT allows calling the API with no limitations.  
See [draft-ietf-oauth-dpop-13](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-dpop#section-12.7) for more details about the choice of focusing on HTTP method and URI, and how to add extra elements in case the scenario calls for it. [draft-ietf-oauth-dpop-13](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-dpop#section-12.7)

---

<div class="post-metadata">

**Author:** ![mnj](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/mnj/32/35292_2.png) [@mnj](https://community.auth0.com/u/mnj)\
**Post date:** [February 27, 2022, 1:03pm UTC](https://community.auth0.com/t/dpop-does-it-really-change-anything/78476/3 "2022-02-27T13:03:45Z")

</div>

Thanks @Vittorio Your answer makes it clear for me 🙂

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [February 28, 2022, 10:24am UTC](https://community.auth0.com/t/dpop-does-it-really-change-anything/78476/4 "2022-02-28T10:24:13Z")

</div>

We are here for you!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 15, 2022, 10:24am UTC](https://community.auth0.com/t/dpop-does-it-really-change-anything/78476/5 "2022-03-15T10:24:13Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
