---
title: "Comment by José Pablo Ramírez Vargas on \"Implementing JWT Auth with NodeJS\" | Hashnode"
description: "Tokens should never be stored anywhere. If your db is hacked, you are giving away all those accesses. A refresh token should also have an expiration time, only"
url: "https://hashnode.com/posts/implementing-jwt-auth-with-nodejs/63a4299d3396f094342b4b46/comment/63a7fe778de4e0eeae64c9c1"
---

[Discussion](https://hashnode.com/posts/implementing-jwt-auth-with-nodejs/63a4299d3396f094342b4b46)

Comment [Implementing JWT Auth with NodeJS](https://hashnode.com/posts/implementing-jwt-auth-with-nodejs/63a4299d3396f094342b4b46)

[José Pablo Ramírez Vargas](https://hashnode.com/@webJose)

[Dec 25, 2022](https://hashnode.com/posts/implementing-jwt-auth-with-nodejs/63a4299d3396f094342b4b46/comment/63a7fe778de4e0eeae64c9c1)

Tokens should never be stored anywhere. If your db is hacked, you are giving away all those accesses. A refresh token should also have an expiration time, only far longer than an access token.
