title: Is "logout" useless on a REST API?
body: <p>Considering that, by definition, a REST API is stateless: is the "logout" operation useless?</p>
  
  <p>I mean, I'm creating a REST API using encrypted JWT. Each token has an expiration time of, let's say, 60 minutes. If I save on a database table the last tokens generated by the API, the "logout" would be done deleting them from the table of valid tokens. But, <strong>if I do that, I understand that the API will cease to be stateless, right?</strong></p>
  
  <p>So, I understand that I shouldn't do that. The only solution that I'm thinking is make the JWT expiration time shorter, to 5 minutes, don't implement a "logout" operation and just let the tokens expire.</p>
  
  <p>Is this the correct approach?</p>