Before OAuth 2.0 existed, if you wanted a third-party app to read your Twitter timeline, you had to give them your Twitter username and password. Not a token, not a scoped credential your actual password.
The app would log in as you, do what it needed, and (if you were lucky) not store the password anywhere sketchy. Users did this constantly. Whole categories of app worked this way Twitter clients, mail readers, contact importers, calendar syncers. Every one of them held a growing collection of user passwords.
This was called the password anti-pattern and it was as bad as it sounds. If the third party app got breached, every user account it touched went with it. Users could not revoke access to a single app without changng their password everywhere. The app had full account access, not just the piece it actually needed.
What OAuth 2.0 does - The user authenticates only with the service they trust (Google, GitHub, etc.). The third-party app never sees the password.…