OAuth 2 Explained In Simple Terms

Get a Free System Design PDF with 158 pages by subscribing to our weekly newsletter: bytebytego.ck....
Animation tools: Adobe Illustrator and After Effects.
Checkout our bestselling System Design Interview books:
Volume 1: amzn.to/3Ou7gkd
Volume 2: amzn.to/3HqGozy
The digital version of System Design Interview books: bit.ly/3mlDSk9
ABOUT US:
Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview series.

[@anilkumar-p6d3w]

I think this is the only video on KZbin, in which OAuth is explained in a very simple way.. thanks.

[@balajik8561]

That's right! Excellent explanation

[@djplt1240]

Great explanation! Two minor clarifications: the authorization code is sent to printMagic service via the user with a HTTP redirect rather than the auth server directly sending the authorization code to PrintMagic. Also depending on OAuth server implementation, you may not be able to revoke the access token immediately and instead have to revoke the refresh token instead.

[@sampathsris]

This is very true, but if you try to draw arrows for all the redirects and HTTP requests, OAuth flow diagrams tend to become really convoluted.

[@karthiksuryadevara2546]

Whats the difference between oauth 1.0 and oauth 2.0

[@henryzhang7873]

There is also the server-sided flow that doesn't require a browser redirect though, where the providers can coordinate directly.

[@nick_merchant]

Very easy to understand, clearly spoken with good graphics and solved the mystery in my mind within 4 minutes and 30 seconds. Thank you so much.

[@sheykenasababy]

0:40 "To scrape information from crusty old banks" I did not expect a roast this hard

[@ElvisANgoh]

This was incredibly refreshing and so easy to understand. This is the first video I have watched from you, I can't wait to see more, and other topics

[@pallavkan]

you solved my confusion in just 10 min which I was struggling after studying so many articles from medium

[@itsZavier_1]

it's always the short videos that explain these kind of things with ease and understanding

[@sridharneelakanta]

Thanks for the concise explanation. Appreciate it. A small correction -- the sequence diagram at 03:52 shows "PrintMagic" within the blue rectangle. It should have been "Snap Store Auth". Thanks again.

[@devrj1679]

Yes your correct, but green rectangle. Thanks for pointing that out.

[@boredhuman9289]

Oh man, you explained this so well, I was struggling with this topic for years now, never actually understanding what is going on there! Thank you!

[@alainpannetier2543]

1. At 2:10 third lifeline title is wrong. Should be OAuth2 server (e.g. Snapstore OAuth2 server or 3rd party [keycloak] server) instead of "Print Magic". Cut'n paste leftover probably. 2. At 2:49 The request dialog that submits the parroval is the one that receives the authorization code in return. So the authorization code is in the browser and acquired by print magic via the redirect_uri initially specified by PrintMagic in the request for dialog. This is why we need the authorization code indirection (otherwise either there is no client auth or the browser would know the client secret).

[@msreedaran89]

2:21 rather than 2:10? I came to the comments to point out the same thing

[@OpenDeepLearning]

@@msreedaran89 Same here

[@dwarslopers]

Thanks! That is correct and helped me!

[@ayoolaoladipe8105]

The explanation is straight to the point and the graphics makes it easier to understand thank you

[@PhillipKerman]

Of course there's tons more to know, but this probably the best description under five minutes. In about one hour Nate Barbettini covers this, along with OIDC and PKCE. After that learn about JWT and related formats and you'll have all the fundamentals.

[@sungjuyea4627]

I always get irritated by this complex and "seemingly" pointless process. Now it is very clear why we need it. Thanks to your explanation :)

[@charlymarchiaro]

At last!!! This is by far the best explanation I've seen. Thanks a lot.

[@sollenism]

Great explanation! and your animation is top notch. Thanks

[@jlp2011]

great vid. minor remark : 1st collab/msg diagram - full one - puts printmagic on 2nd n 3rd lane from left. 2nd diagram has 3rd lane being snap’s auth which makes more sense

[@am_0x2a]

I noticed this too. Great video overall though!

[@mduzair1120]

Perfectly explained!

[@tayyabmunir6228]

Wao, I was struggling with the basic concepts of oauth2 for a long time. This video explains it really well.

[@locotx215]

You did it, you finally explained the WHY part . . . ."so you don't have to share credentials with other sties"

[@sumanthvarma9999]

Can you cover Kerberos authentication please

[@anilsonone6067]

Up to the point explanation. Very Straight forward way with good graphics. Thanks....

[@ilhamiyanmaz4743]

Thanks for this tutorial !

[@hakkoktay7597]

Explained in a very simple way but also excellent!

[@jubiaj2672]

best explanation so far. thank you

[@jasoncampbell1464]

In a nutshell, you ask app 1 to invoke app 2. App 2 comes to you and asks if the request is legit. If you say yes, the apps create a secure communication channel and start collaborating to offer you the service

[@vintagewander]

I was about to implement google login from scratch and had a lot of problems implementing it without relying on external libraries. This video helped me a lot sir, thank you for your content ❤

[@andrewtcoder]

Perfect explanation! Thank you so much!

[@bhagyeshpatel18]

I love your content and really easy to understand.I HAVE REQUEST THAT YOUR DIAGRAM/ ANNIMATION HAS MOTION/ZOOM OUT-IN/ which makes me keep eye and It is difficult to focus. Just advice, if you can stop using the motion/zoom out-in , just show still annimation. Thanks

[@saravanansomu8296]

Very nice explanation with the perfect animation. It's slick because it doesn't need lot of implementation details here.

[@nemonemo6285]

Perfect, thank you.

[@thomashsu5252]

Super explanation. Thanks a lot for sharing

[@madhavareddy580]

Beautiful visuals and amazing explanation. Thanks!

[@profindia]

explanation is great. At 3:59, the "SnapStore Auth" box is missing

[@haykkarapetyan867]

Great explanation, BUT on 3:51 the "Snap Store Auth" changes into "PrintMagic" on your sequence diagram. This makes it look like the refresh token is given to the same "PrintMagic" to get updated Access Token

[@mawhadmd]

Very well explained.

[@SoupTubeTV]

This channel is invaluable. Thank you for your knowledge!

[@suha2072]

Thank you for the great lecture! It was very helpful. I was successful in getting the device access code, but is there a way to expire the access code or log out? We want to develop a service that allows multiple people to use one device. We need to process when the user logs out the device token.

[@nishithvyas]

Superb Explanation... Now, no need to go with "What is OAuth Question" anywhere....!!!

[@basseygodwin7384]

Clearest video I've seen on this

[@gsenthilkumar8139]

00:04 OAuth 2 simplifies secure access to resources. 00:37 OAuth 2 is like giving someone a special key for accessing specific information in another application. 01:12 Using OAuth2 to grant permission to access Snap Store photos. 01:39 OAuth 2 facilitates secure access to resources 02:16 OAuth2 process flow explained 02:50 Authorization code is exchanged for access token by the client. 03:24 OAuth 2 protects login credentials and allows controlled access to authorized resources. 03:58 OAuth 2 is essential for web security Crafted by Merlin AI.

[@wirelessnerd7131]

Thank you for the explanation. Simple and straight forward and btw great graphics.

[@ayaabdelmagied6696]

you head nail on the head.... simple and to the point

[@videogamesare1]

Outstanding video! Thank you!

[@axis0401]

Animation in this video is awesome

[@yogavedfood]

@ByteByteGo what is the use of state variable in OAuth2 and how to handle its storage in a stateless multi machine UI server because the callback can go to any of the servers if stored at server side.

[@ronitdhingra4395]

What tool do you use for the animations? they are great!!

[@laserz23]

curious to know this too

[@XJacksonvilleX]

the graphics are amazing.. how do you create them??

[@brianliang3010]

why can't access token be sent along in permission granted response and requires another request?

[@Marksmwangi]

easy to understand

[@davideanguianomelendez628]

It seems to me that diagrams on 2:20 and on 3:58 have a mistake: the green "PrintMagic" actor should be labeled as "SnapStore Auth", as it actually is on 3:17. Am I right?

[@ml-rj5pt]

Thanks for the great video. One question though...at 3:20 when PrintMagic fetches photos with the access token, does the SnapStore Resource still need to validate the access token? If so, does it need to call SnapStore Auth api to validate?

[@sandovalvaz6093]

Hi, do you know why this error occur? "OAuth 2 parameters can only have a single value: scope"

[@mightylb4543]

Why we need 2 different codes ? Authorization codes and access tokens, why was it designed this way?

[@avidtechie9734]

an authorization code is a temporary credential that serves as proof of the user's consent to access their protected resources. It plays a crucial role in the OAuth flow and is used to obtain an access token, which is then used to make authenticated API requests on behalf of the user. The authorization code flow adds an extra layer of security to the OAuth process. Instead of directly exchanging user credentials (e.g., username and password) for an access token, the authorization code flow separates the authorization and token exchange steps. This way, the access token is not exposed to the client application, reducing the risk of unauthorized access or token leakage. OAuth: Authorization Code Importance In OAuth, an authorization code is a temporary credential that serves as proof of the user's consent to access their protected resources. It plays a crucial role in the OAuth flow and is used to obtain an access token, which is then used to make authenticated API requests on behalf of the user. Here's an overview of why an authorization code is needed in OAuth: User Consent: OAuth is designed to protect user data and privacy. Before an application can access a user's protected resources (such as their profile or data), the user must explicitly grant consent. The authorization code serves as evidence that the user has granted permission for the application to access their resources. Security: The authorization code flow adds an extra layer of security to the OAuth process. Instead of directly exchanging user credentials (e.g., username and password) for an access token, the authorization code flow separates the authorization and token exchange steps. This way, the access token is not exposed to the client application, reducing the risk of unauthorized access or token leakage. Limited Lifetime: Authorization codes have a limited lifetime, typically short-lived, making them less susceptible to misuse. Once an authorization code is issued, it has a short validity period, usually a few minutes. This helps mitigate security risks and reduces the window of opportunity for attackers to intercept and abuse the code. Authorization Code Exchange: After obtaining the authorization code, the client application sends it to the authorization server, along with its client credentials, to exchange it for an access token. This token can then be used to make authenticated API requests on behalf of the user. By using an authorization code, OAuth ensures that the user's consent is obtained, enhances security by separating authorization and token exchange steps, and provides a limited and controlled means of obtaining access tokens. In Authorisation code flow this happens. There are various authentication / authorisation flow available. In the above video authorisation code flow is explained. In which authorisation code is returned after successful authentication. Then authorisation code + client id + secret key is sent to the server which validates that the user is the same as authorization key is the same and it is not tempered. And then the server returns 3 tokens. (1.Access tokens which contain scopes/ permission used for sending requests to get resources. 2.Id token which contain user information/ claims. 3. Refresh token - this is optional.)

[@tsunghan_yu]

Mainly two security benefits: 1. we can avoid sending the access token, which is sensitive information, in the front channel and send it in the back channel instead. 2. we can authenticate the client as well by requiring the client to send client_id and client_secret (along with authorization code) to request the access token. Here's a video that directly answers your question: kzbin.info/www/bejne/b2qZgJybra2tm5I And here's a good illustration of the whole flow: kzbin.info/www/bejne/hpfZhHdsgtJ4o7M

[@henryzhang7873]

This prevents the client from knowing the token. The services may not trust the client or want to charge money for operations without the risk of spoofing.

[@tadtab2]

@2:20 the 3rd column need to be renamed 'SnapStore ' instead of 'PrintMagic'?

[@jamaicanstillbapin]

Excellent video, many thanks!

[@Akshay56633]

Thanks for the video! Finally I know what this OAuth 2 is.

[@JinTsen]

There is a small mistake. When you first animate the flow at 2:19 , you have 2x PrintMagic, missing the (later fixed) SnapStore Auth

[@MrNeuroMind]

3:59 also

[@padalaraveendra]

Breakdown of complex concepts in to digestable explanations --> Quite Appropriate wording😍

[@muhammadumarsotvoldiev8768]

Thank you very much! Very helpful!

[@babhijit]

At 02:29 whose client id is being referred to - PrintMagic or SnapStore ?

[@ikbo]

Why the extra http request of getting authorization code then access token?

[@vicenterendo]

Thank you so much, lifesaver!

[@twinkleverma2945]

Hi @ByteByteGo ... @3.51 the 3rd tower's name is incorrect. It should be "SnapStore Auth" instead of "PrintMagic". It becomes confusing at this point.

[@deemon710]

@3:22 That feels a tad redundant. Anyone know why SnapStore Auth doesn't immediately give the access token (in green) after the request is approved (in blue)? Why is the "Get Access Token" (in yellow) step needed?

[@umarsaid6340]

If I want to make a mobile app, what authentication scheme should I use? Oauth 2.0 authorization code, client credentials, or just basic username password?

[@meghnamanjunatha4707]

Thank you so much for the clear and simple explanation!

[@systemBuilder]

It would be super awesome to give an example of a barebones OAuth2 that everybody uses (like a draw webapp asking for access to your google drive with frw other assets) then we could literally watch the OAuth2 in the Chome debug window under the network tab.

[@sergiomora1209]

Can Google App Passwords still be used to access Gmail through Outlook 2019 using POP3 after LSA’s is disabled?

[@canhlinh]

Nice presentation. Thank you.

[@cuybueno]

Another kickass video!

[@NallapuSrinivas-k1p]

when oAuth is enabled, the client software first requests for authorisation from the auth server & auth server asks the user for approval and when approved, auth server gives an access token to the client software and client can make requests and get responses

[@somnathgolui2912]

Thanks for the video.

[@himanshujain5670]

simple and crisp explanation

[@bhagyeshpatel18]

There is problem in the image at 3:54 second. Third Entity should be SnapStore Auth Server. NOT PrintMagic.

[@bhaveshmuleva2352]

Will implement in my upcoming project

[@fong555]

Another great video! Thank you for your time and effort! Could you please share or make a video about what tool and how you made those animated diagrams? Appreciated so much!

[@etshbadr]

Love your explanation!

[@800pieds]

Clear, but how does Snapstore know that the token is valid?

[@HikeWkam]

That was awesome

[@annetak693]

Not sure I heard it right at 2:55. So, #authorizationcode IS #clientId and #clientsecret?? Or #authorizationcode WITH #clientId and #clientsecret (and are presented to authorization server?)

[@juozasjuozas]

That was great! But how about registering? Eg. using a google Account to log in. Considering i can revoke the token. How can I log in despite never having given my password to the external side?

[@edydon]

Very clear presentation. Keep up the great work!

[@testtest-c4z]

Very good video, I have a question if I am developing an app, my server would do authentication service based on what I implement and authorization server, right? In the latter I should implement the access by roles, within the same token as information I would get the scope to compare whether or not you have access to the resource? Thank you very much

[@musaddiqueansari7695]

wow! great explanation

[@RamChandran-s1e]

Great Explanation👏. One question what happens if refresh token expires, will the user have to go through oauth process again.I'm just curious.

[@testtest-c4z]

Hello, how are you, there are applications that request a token, request that the client id and seceret key be sent, others an api token and a secret key, how is this different from, for example, sending user and pass?

[@mahamadoutogola4001]

Great explanation 😊

[@tahiraziz193]

Your explanation is Aws0me👍

[@zehrairkicatal2156]

excellent explanation

[@abdoyones1983]

is there a mistake in the diagram @ 2:19 ?

[@vatsalshah8680]

Question - How does the SnapStore resource server verify the OAuth token? Does it call the OAuth service to do this?

[@jaiyden9888]

Thanks for this! Great video :)

[@trickytricktwo]

very nice explanation

[@7tsh]

The video looks great. would you mind telling me which tool does you use to create the video ?

[@willpringle]

Awesome video!

[@oskarspozdnakovs6441]

Great video. It's Zero Auth by the way

[@BehniaFB]

I liked the animations

[@yashsolanki069]

I would like to know if this (OAuth 2.0)service is free to use or has some charges after some requests. If anyone has any idea, please let me know.

[@sLiv256]

perfectly explained

[@StanleySathler]

Why after receiving the authorization code, we still need to request the access token? Couldn't we just retrieve the access token directly?

[@StanleySathler]

After a long convo with ChatGPT, that's what I came with: There's always some UI involved, as the user needs to consent permissions. As UI's are less secure environments, it'd be risky to give them the access token. That's why we often do the "authorization code access token" exchange in a server environment. Still, would love extra thoughts on this.