OAuth in laymen terms
OAuth and all the other authentication, authorization are full of jargon (and massive specs) and itâs really over complicated to the beginners who wish to learn about it. First thing we have to understand is what is happening in the big picture.
Early days scenario
When 3rd party applications required accessing data and features on Facebook, Twitter the approach was to give away the username and password of your Facebook/Twitter account to the 3rd party application. By giving away the username and password plainly to 3rd parties allowed unauthorized access of the account since everything can be accessed by the username password.
So whatâs the real problem here?
Todayâs cyber citizen has resources in the internet. These resources can be e-mail, user accounts, documents and many more. And almost always people needs to collaborate with other people and applications as well to achieve productivity in their tasks. But it was not necessary to give authorization to all the resources a user has to every application.
OAuth is a mechanism to use implement the above scenario. The user will have resources online. An access token will be generated per application for the necessary resources of the user. This token is valid for the particular user as well. By doing so we isolate the functions from authentication and allow unified resource usage.
Everything else regarding OAuth is itâs implementation. For more understanding of this watch the below video -
















