JWT للمصادقة عديمة الحالة

In this lesson, we'll dive into JSON Web Tokens (JWTs). They are a compact, URL-safe means of representing claims to be transferred between two parties.

JWTs are crucial for stateless authentication. This means the server doesn't need to store session information. Instead, all necessary user data is embedded directly within the token itself.

A JWT is made of three distinct parts, separated by dots (.):

• Header: Information about the token itself.
• Payload: The actual data (claims) you want to transmit.
• Signature: Used to verify the token hasn't been tampered with.

It looks like this: xxxxx.yyyyy.zzzzz

The Header usually contains two parts:

• alg: The algorithm used for signing (e.g., HMAC SHA256 or RSA).
• typ: The type of token, which is usually 'JWT'.

The Payload contains the 'claims' – statements about an entity (typically, the user) and additional data. Common claims include:

• sub (subject): The user ID.
• iss (issuer): Who issued the token.
• exp (expiration time): When the token expires.

The Signature is what makes JWTs secure. It's created by taking the encoded Header, the encoded Payload, a secret key, and the algorithm specified in the header, then signing them.

HMACSHA256( base64UrlEncode(header) + "." + base64UrlEncode(payload), secret )

If someone tries to alter the header or payload, the signature verification will fail, indicating the token is invalid or tampered with.

Here's how JWTs typically work in an authentication flow:

1. User logs in with credentials.
2. Server verifies credentials and creates a JWT.
3. Server sends the JWT back to the client.
4. Client stores the JWT (e.g., in local storage or a cookie).
5. For subsequent requests, the client sends the JWT (usually in the Authorization header).
6. Server verifies the JWT's signature and expiration before processing the request.

We'll use the popular jsonwebtoken library. First, install it with npm install jsonwebtoken.

This example shows how to sign (create) a new JWT with a payload and an expiration time. Remember to keep your secretKey very secure!

Once you receive a JWT from the client, your server needs to verify its authenticity. The jwt.verify() method checks the signature and expiration.

If the token is valid, it returns the decoded payload. If not, it throws an error (e.g., TokenExpiredError or JsonWebTokenError).

Where you store JWTs on the client-side is critical for security:

• Local Storage / Session Storage: Easy to use, but vulnerable to Cross-Site Scripting (XSS) attacks if malicious JavaScript can access it.
• HttpOnly Cookies: More secure against XSS because JavaScript cannot access them. However, they are vulnerable to Cross-Site Request Forgery (CSRF) if not properly protected.

Often, a combination of strategies or careful CSRF token implementation is used.

For enhanced security, many applications use two types of tokens:

• Access Token: Short-lived (e.g., 15 minutes to 1 hour), used for direct API calls. If stolen, its utility is limited.
• Refresh Token: Long-lived, stored securely (e.g., HttpOnly cookie). Used to obtain a new access token once the current one expires, without requiring the user to log in again.

This pattern minimizes the risk of long-lived access tokens being compromised.

Let's quickly test your understanding of JWTs!

You've successfully learned about JSON Web Tokens! We covered:

• What JWTs are and their role in stateless authentication.
• The three parts: Header, Payload, and Signature.
• How to create and verify JWTs using Node.js.
• Important considerations for client-side storage and the use of refresh tokens.

JWTs are a powerful tool for building secure and scalable authentication systems in your Node.js applications!