The problem OAuth solves
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
explain why we need delegated access.
Planned topics
- Old way: give a third-party app your password so it can read your data. That gives it everything, forever.
- OAuth 2.0 lets an app get limited, revocable access without ever seeing the password.
- The user logs in at a trusted server, which hands the app a token with limited scope.
- OAuth is about authorization (what an app may do), not about proving who the user is.
- It also lets many apps share one login system.
Draft outline details
Demonstration
two pictures: "give the app my password" versus "app gets a token with scope orders:read".
Check your understanding
Does the third-party app ever see the user's password in OAuth?
Show answer
No.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.