JWT Authentication using MERN Stack – FreeCourseSite

What is JSON Web Token?

JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWTs can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA or ECDSA.

JSON Web Token (JWT, pronounced /dʒɒt/, same as the word “jot”[1]) is a proposed Internet standard for creating data with optional signature and optional encryption whose payload holds JSON that asserts some number of claims. The tokens are signed using a private secret or a public/private key.

JWTs consist of three parts separated by dots (.), which are:

• Header
• Payload
• Signature

Let’s explain some concepts of this definition further.

• Compact: Because of its size, it can be sent through an URL, POST parameter, or inside an HTTP header. Additionally, due to its size, its transmission is fast.
• Self-contained: The payload contains all the required information about the user, to avoid querying the database more than once.

In authentication, when the user successfully logs in using their credentials, a JSON Web Token will be returned. Since tokens are credentials, great care must be taken to prevent security issues. In general, you should not keep tokens longer than required.

You also should not store sensitive session data in browser storage due to a lack of security.

Whenever the user wants to access a protected route, it should send the JWT, typically in the Authorization header using the Bearer schema. Therefore the content of the title should look like the following.