Custom Authentication Middleware

The video tutorial explains how to create a protected route for user profiles using middleware to validate JSON Web Tokens (JWT). It covers setting up the route, creating middleware for token validation, implementing token verification, and fetching user data. The tutorial also demonstrates testing the route using Postman and handling errors related to token validation. Finally, it shows how to finalize the user profile route with token protection.

What is the purpose of creating a protected route in the context of user profiles?

• To allow public access to user data

• To restrict access to authenticated users only

• To enhance the speed of data retrieval

• To simplify the user interface

Which library is used for token validation in the middleware?

• jsonwebtoken

• express-validator

• mongoose

• bcrypt

How is the token sent in the request headers?

• As a cookie

• As a bearer token

• As a query parameter

• As a plain text

What is the role of the Express Async Handler in the middleware?

• To log user activities

• To handle exceptions in asynchronous code

• To manage database connections

• To handle synchronous operations

What happens if a token is not provided in the request?

• A warning is logged but the request proceeds

• The request is processed normally

• A 401 Unauthorized error is thrown

• The user is redirected to the login page

How is the user's ID extracted from the token?

• By decoding the token

• Using a database query

• By parsing the request URL

• Through a session variable

What is the purpose of excluding the password when fetching user data?

• To prevent unauthorized access to sensitive information

• To improve the performance of the application

• To reduce the size of the response

• To comply with data storage regulations

What is the expected outcome when a valid token is used in a request?

• The request is denied

• An error message is displayed

• The user is logged out

• The user's profile data is returned

What happens if the token is manipulated or incorrect?

• The user is redirected to the home page

• The request is processed with a warning

• A 404 Not Found error is returned

• A 401 Unauthorized error is returned

How can the middleware be reused for other routes?

• By copying the code into each route

• By using a global variable

• By importing and applying it to desired routes

• By creating a new middleware for each route