Curated articles, resources, tips and trends from the DevOps World.
Summary: This is a summary of an article originally published by the source. Read the full original article here →
by In order to understand authorization, we will be taking an example of user interaction with Gmail.
For this, the user will be sending HTTP requests to the Gmail server and in response will expect the response from Gmail Server.
Corresponding to this session id it will store in memory all the user information that is needed by the Gmail server for recognizing the user and allowing it perform operations.
We make use of the JWT for authorization so the server will know that the user is already authenticated and so the user does not need to send the credentials with each and every request.
Made with pure grit © 2024 Jetpack Labs Inc. All rights reserved. www.jetpacklabs.com