This article will help you to understand the OAuth 2.0 authorization code flow.
Authorization Code Flow for OAuth 2.0
The OAuth 2.0 Authorization code flow is for web applications with server side components, which allow confidentiality for the customer to be kept on the permission server (confidential client). In general, permission servers need a secret when requesting authentication if more sensitive personal data, such as personal data or refresh tokens have been desired. If you don't, you will only obey the Implicit OAuth 2.0 flow which returns only an access token from the permit server.
In the Authorization Code flow, the server-side component of the web application can freely manage the user's session upon authenticating with the authorization server without revealing anything about the authorization server's response (such as personal data or refresh token) to the end-user.
A Typical Authorization Code Workflow:
You can read more in detail in this article about Authorization Code Flow for Auth 2.0: https://www.loginradius.com/blog/async/authorization-code-flow-oauth/
What is 2FA Two-Factor Authentication (or 2FA as it often referred to) is an extra layer of security that is used to provide users an additional level of protection when securing access to an account.
Let’s take the story step-wise. You should have heard by now of 2-FA, two-factor authentication. The base idea is pretty simple. Apart from just the password, many of the websites might be sending you an OTP on the phone to grant access.
With transformational changes seen in the business and technology front, Entrepreneurs’ view towards technologies is changing. Here are [the top technologies that young entrepreneurs can embed to increase their business...
Get updated with the newest top 10 trending technologies in 2021 which professional must learn to boost there career.
First, the differences between authentication and authorization will be explained. Secondly, OpenID Connect and OAuth2 will be introduced as solutions for centralized authentication and authorization for microservice architectures. Lastly, there will be two implementation choices explained for authorization.