2022-08-12
1634
Fernando Doglio
72
Aug 12, 2022 â‹… 5 min read

How to secure a REST API using JWT authentication

Fernando Doglio Technical Manager at Globant. Author of books and maker of software things. Find me online at fdoglio.com.

Recent posts:

The complete guide to the AbortController API

Check out a complete guide on how to use the AbortController and AbortSignal APIs in both your backend and frontend.

Joseph Mawa
Mar 12, 2025 â‹… 9 min read
Not Everything Should Be A Chat: Rethinking LLM Integration

Beyond chat: Rethinking how we use LLMs

LLMs can do more than chat! Explore alternative integration models that improve efficiency, reduce complexity, and enhance user control.

Rosario De Chiara
Mar 12, 2025 â‹… 4 min read

A guide to image overlays in CSS

Learn the basics of applying image overlays in CSS and explore more interactive techniques like hover effects and animations.

Ibadehin Mojeed
Mar 11, 2025 â‹… 5 min read

How to use EJS to template your Node.js application

EJS makes working with templates in Node.js super easy — but only if you know how to use it. This guide walks you through the essentials and more.

Samuel Olusola
Mar 11, 2025 â‹… 15 min read
View all posts

7 Replies to "How to secure a REST API using JWT authentication"

  1. You swapped the meaning of the issuer and the subject. The issuer is the authentication server which issued the token (usually a URI). The subject is the user being authenticated.

  2. this is best article, I have read every with context of explaining. you have explaines evrythig nicely and to the point. Thank you very much.

  3. That is a nice explanation! What about the need of changing the shared key, in case of symmetric encryption and signing? What option is there?
    I think the asymmetric encryptions would not be feasible for many client apps and even those keys have to be changed after some time!

  4. What problem does this solve that isn’t solved by, for example, Basic Authentication with a simple shared secret? How do you revoke access for a live JWT?

  5. Overall good explanation with the exception of having the JWT-secret known to the client.
    The only validation of the JWT that the client should do is to check the expiration-date of the JWT before using it.
    If it’s expired, then the client can go the route of re-authenticating the user.

    The back-end (API) is the only place that should know the JWT-secret so that it can verify if any JWT it receives was actually created by the back-end and was not tampered with.

  6. Great article. Note that JSON Web Tokens come in two flavors (or structures) – JSON Web Signature (JWS) and JSON Web Encryption (JWE). From the RFC: “JWT – A string representing a set of claims as a JSON object that is encoded in a JWS or JWE, enabling the claims to be digitally signed or MACed and/or encrypted.”

    The JWE compact serialization results in 5 parts, JWS is 3 parts.

Leave a Reply