How does a short-lived Access Token add security?
<p>In the answer to the question <a href="https://stackoverflow.com/questions/7030694">Why do access tokens expire?</a>, the first point provided states:</p>

<blockquote>
  <p>[Bearer-Tokens are] short-lived and requiring refresh, they limit the time an attacker can abuse a stolen token.</p>
</blockquote>

<p>But when an Access-Token is used (From a native-app), the <strong>Client</strong> uses the <strong>Refresh-Token</strong> to get a new <strong>Access Token</strong>, and sends that new token back to the requestor.  So if an attacker uses somebody else's access token, he'll just be sent a brand new access token every time.</p>

<p>So who cares about how long the token lasts?  If an attacker gets it, they have taken over the session <strong>For As Long As The Refresh Token Lasts</strong></p>

<p>I already know a dozen answers to my question, but I have questions to each answer.  My original question was so long because I explained every scenario and how they are inconsequential or false (as far as I know).  So please try to help me understand and I'll comment if I think the answer has caveats.</p>

<p><strong>Addition/Edit - Hoping for more answers with my additional information</strong></p>

<ol>
<li>Web Page calls a Client with Resource Owner (User) Credentials</li>
<li>Client calls the Auth Server and gets an Access and Refresh Token.  The Access Token will expire in 5 minutes, the Refresh Token will expire in hours or days or whatever.</li>
<li>Client sends the Access Token to the Web Page</li>
<li>Resource Owner (User) uses the web page</li>
<li>Web Page sends the Access Token to the Client</li>
<li>Client sends the Access Token to the Resource Server</li>
<li>Resource Server checks the Access Token in any number of ways</li>
<li>Resource Server sends Resources to the Client</li>
<li>Client sends Resources to the Resource Owner</li>
<li>Resource Owner (user) Continues to use the Web Page</li>
<li>The Client, either during Each Request or every 4 minutes and 30 seconds, uses the Refresh Token to get a new Access Token</li>
<li>The Client, either during Each Request or every 4 minutes and 30 seconds, sends a New Access Token to the <strong>Active</strong> Resource Owner</li>
</ol>

<p>Yes?  No?  Since the Resource Owner is <strong>Actively</strong> using the web site, the web site is in constant communication with the Client, and the Client gets a new Access Token (Using the Refresh Token) and sends it back to the web site, so the <strong>Active</strong> user can continue using the site without being kicked out every 5 minutes.</p>

<p>Therefore, if ANY Person gets ahold of that Access Token, and are hitting the Client with it, the Client will continue to send new Access Tokens to whoever has that Access Token.  Granted: After a single refresh, one of those two people will have a bad Access Token and be booted, but not necessarily the right person.</p>