title: Handling expiry/"remember me" functionality with JWT
body: <p>Conceptually, I really like JWT as it is in line with the statelessness of REST etc (no state saved server-side, all relevant data is contained in the token). </p>
  
  <p>What I am unsure about: how would you handle token expiry when not connected (ie, a "remember me" functionality)?</p>
  
  <p>There's an emerging coverage of JWT on the web, but I couldn't find anyone that answered the expiry question yet. </p>
  
  <p><strong>Clarification:</strong> I am not asking how to handle a token soon-to-expire, but what to do when a token has already expired (user closed website/app for a while). The simplest solution that comes to my mind is caching the user's credentials, which is rather insecure.</p>