Why not just use a long TTL reference token in replace of access and refresh JWT tokens?
<p>I'm building both a mobile and single-page app and have been evaluating auth techniques that <strong>allow for immediate access/token revocation</strong>.  I see Auth0 and Stormpath use both access and refresh tokens in addition to allowing for revoking tokens.  </p>

<p>What's the point of a refresh token and short TTL access token if you're maintaining a list of valid tokens and checking against that upon reach request received on the resource server?  Why not create one reference token with the same TTL as you would set on the refresh token and now you don't have to worry about refreshing the access token (right before it's about expire) and have one less token to worry about?</p>