DEV Community

Zeeshan Ahmad
Zeeshan Ahmad

Posted on

Access Token and Refresh Token

#webdev #javascript #programming #node

Access Token

Access tokens are short-lived, that allow the user to access resources without needing to log-in repeatedly. These are sent with an each API request (Authorization: Bearer ). If they are stolen, attacker would have a very shorter time window. Their life span vary company to company but in general their life span is 30-90 mints.

Access tokens are very useful when you want a password less login. Similarly, they are useful when you want to access the shared resources. For example, when you want to edit or use the file owned by someone else, access tokens make it easier and secure for you.

Refresh Token

Refresh tokens are long lived, that are used to generate the access tokens without asking the user to login with your credentials frequently. They are stored securely on the authorization server and sometimes stored in httpOnly secure cookies. It is because they must be stored securely in order to avoid its vulnerability to attackers. Their life span also vary company to company but in industry practice it has the life span of 30-90 days.

When an access token expires, refresh token is used to get a new one without logging in. Because user is authenticated on the basis of refresh token.

Every time a refresh token is used to generate the access token, the old refresh token becomes invalid and it is also regenerated in order to avoid security threats. This technique is called as Rotation.

JWT

JWT (JSON Web Token) is popular token format because it is stateless , compact (self-contained claims) and easy to transport in HTTP headers. A JWT can be a access token and a refresh token as well. But refresh token less use JWT format.

JWT generates a signature by hashing header + payload with your secret key. Let’s take an example to understand it easily.


const payload = {
    id: "user123",
    name: "John",
    email: "john@123.com"
}

const SECRET_KEY = "your_secret_key"

jwt.sign(payload, SECRET_KEY, {expiresIn: "10m"})
Enter fullscreen mode Exit fullscreen mode

Some beginners think jwt.sign(), encrypts the payload, it does not. It just signs, which means if anyone try to tamper it, the signature verification fails. So it just make your payload tamper-proof. For instance, after signing the token looks like this :


eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.
eyJzdWIiOiJ1c2VyMTIzIiwibmFtZSI6IkFsaWNlIiwicm9sZSI6InByZW1pdW0ifQ.
wL3Jhpc6pCkJkT7Yt3cvvjTgC1z0sX4eS9B3Gx6w3Nk
Enter fullscreen mode Exit fullscreen mode

In order to verify it, we use:


const decoded = jwt.verify(token, SECRET_KEY) //token: token sent by user
console.log("Token Data: ", decoded)
Enter fullscreen mode Exit fullscreen mode

Our claims (payload + header) are decoded with this verification that they were not altered. Now understand the terms stateless and self-contained used earlier. Later means a JWT includes all the claims (payload + header) to identify the user nothing is required from the database that is enough to authenticate the user. Stateless means server does not need to store the session data in the database. Instead the all the claims are present in the token itself. They do not need to make the DB query to look who you are, serve just verify the signature.

Access token and refresh token aren’t separate, they work together to make the login process smoother and secure. Access tokens are used for initial access while refresh tokens are used to extend that access to the resources over time.

Top comments (0)