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:

How To Switch Node.js Versions With NVM

How to switch Node.js version: A cross-platform guide for NVM and alternatives

Use NVM, Node Version Manager, to switch between Node.js versions, simplifying your development process.

Precious Luke
Mar 10, 2025 â‹… 9 min read
How To Install And Use NVM: A Complete Guide For Managing Node.js Versions

How to install and use NVM

Tired of version conflicts with Node.js? NVM lets you switch between multiple versions easily, ensuring your projects always run smoothly with the right environment.

Carlos Mucuho
Mar 10, 2025 â‹… 7 min read

JavaScript’s sort()method: From basics to custom sorting

Discover how to sort arrays in JavaScript using sort() and toSorted(), including customization and language-sensitive sorting techniques.

Joseph Mawa
Mar 7, 2025 â‹… 11 min read
Migrating To Valkey From Redis

Migrating to Valkey from Redis

With Redis’ license change and the launch of Valkey 8.0 as an alternative, this guide covers key differences and migration steps.

Matteo Di Pirro
Mar 6, 2025 â‹… 5 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