OAuth 2.0 & OpenID Connect (OIDC): Technical Overview

This video explains the basics of the OAuth 2.0 & OpenID Connect (OIDC) protocol, focusing on what an IT administrator must know.
VMware End-User Computing (EUC) solutions empower the digital workspace by simplifying app & access management, unifying endpoint management & transforming Windows delivery. Learn more on the Digital Workspace Tech Zone: techzone.vmware.com.

[@krishnachaitu17]

There is always disconnect for my understanding and some tutorials , the best and very deep explanation I found thank you so much really appreciate it for making so much granular

[@phanindratube10]

Oauth2 not handling authentication part in it's standard is most crucial which most of other tutorials fails to explain. Thanks!

[@mohammeddanish879]

How easily and clearly you have explained the topic is commendable. This video clears many questions poping in my mind while I was reading about differences between OAuth2 and OIDC.

[@shwethanayak2459]

Great work.. Thanks for explaining it at such detail.

[@sagarprateek9216]

Have been using a central third party authorization server for a couple of years but I wasn't able to connect the dots clearly. This video helped me visualize the whole process. Thank you so much !

[@oudinia1]

Genius explanation of OAuth and OIDC in no time. Thank you so much.

[@nyplace1]

Absolutely amazing explanation, i saw many videos, none of them make it as clear as you did. You have a rare talent. Thank you

[@VikasKumar-nq8if]

This is not an easy topic and all are modern apps use this flow. But once again kudos to Peter for explaining this so well. Keep them coming Peter.

[@viveksingh-ce2oy]

This was awesome!! what you did in 16 mins, I think it will take hours to explain this much by others.

[@a4ldev933]

Great job explaining Auth2.0 and OIDC 👍. Thank you!

[@codezard1]

Wow! Incredible explanation. I would like if you can make a separate video on some important OAuth Flows.

[@VMwareEndUserComputing]

Thanks and glad you liked it. This video is a series of three, IAM overview, SAML and OAuth 2.0. Currently there are no plans on doing more videos in this series. I hope what is today available allows for a good introduction into the world of federation. At least that was my intention. Any deeper learnings will have to be made using other means.

[@tamaramal1]

best video i found on this topic, very clear! Thank you much

[@dennismunyaka6537]

the only video that explains this very well

[@mickeyp1291]

so clear and well explained. answered all of my questions

[@andrebittencourt5512]

This is by far the best video I have watched about this topic! Thank you so much!

[@VMwareEndUserComputing]

Glad it was helpful!

[@tyronefrielinghaus3467]

👍 Thank you so much...so clearly explained. Understandable, good voice. Saved me so much time.

[@hristuppiteitinu]

Fantastic explanation. Thank you Peter!

[@alexandrefenyo1506]

Brilliant ! Best video on those protocols I have ever watched.

[@andrewmontague9682]

Excellent content as always from Peter.

[@quanganghong7697]

Thanks, very clear and useful

[@StMarc-ow4wz]

This is an amazing video. I can't say anyone can do it better than you.

[@ordinaryBrownDad]

Great explanation, I have seen other videos on this topic but this video give best explanation so far

[@MrEitan1980]

thx for explaining the principles . it's very clear to me now.

[@nihilsinedeo1010]

You the man :) Thank you for these awesome and so useful tutorials.

[@ankityadav1598]

Very well explained and found the best content on the above topics. Thanks a lot ..!!

[@sky76570]

Wow, you have a talent explaning things 👍🏻

[@manaryousry2160]

It was very helpful and explained clearly Thank you so much

[@ppvshenoy]

Superb explanation. Thanks for your efforts. Much appreciated.

[@Nithin_Coorg]

Clear crisp explanation!

[@maksymshyshkov2787]

Wow! Thank you for that explanation! Very useful and easy to understand! Too danm good! :)

[@windar2390]

that was a really good explanation!

[@cottondai]

mindblowing clarity!!!

[@nirmalajce]

thanks Pete, super clear explanation

[@michaelromrell4791]

very helpful. thank you

[@RahulSinghInfosec]

Very well explained. Thanks!

[@Deltanova93]

Quality video for free. Thanks

[@nooralqoj4575]

Great explanation Thank you !! :)

[@durgaprasady8044]

Good work(job). Keep it up @PETER BJORK.

[@pallabipatro]

Very clearly explained

[@ec9386]

Great explanation!

[@vickiclarke1760]

This is such a great video. Thank you. You have managed to answer all my questions so clearly!!

[@alfredoalarconyanez4896]

Thank you, it was very useful !

[@shirish2005]

BEST EXPLAINATION

[@EasyPlatters]

Excellent Thank You

[@jpnr19999]

Was very usefull thank you very much!

[@limyanling6783]

Amazing content

[@SachidanandKumar]

Very informative

[@RohitBaravkar]

Good content 👌

[@emmanuelpregnolato5026]

Very helpful

[@arsenbandurian5554]

Good overview and I life the whiteboarding style. I used to play with these "infiniboards" about 5-6 years ago, but found them clunky. What tool is it?

[@sandyj342]

👏🏽 awesome

[@barbaradesoete8292]

Great

[@sukulmahadik0303]

❤❤

[@hks101]

This is absolutely wonderful. Who says learning has to be complicated :) Is it possible to get the slides used by any chance? Thanks!

[@VMwareEndUserComputing]

Glad you liked the video. Sorry but the slides cannot be shared.

[@MMSummer26]

Hi, Your videos are really pretty good! I just wonder about, why you are using different terms as in the last video about SAML. Authentication server = identity service provider Resource server = Service provider Is there a specific reason (which I don't see), that the above mentioned terms cannot be used? Many thx 🙂

[@VMwareEndUserComputing]

The reason is what term is being used in the standards. I try to keep the videos as accurate, but still easy to understand, as possible. OAuth och OIDC uses different terms than SAML.

[@jainnylijin8]

What happens if the access token expires? Do they use refresh tokens to handle this? I haven't seen any mention of a refresh token in the diagram.

[@VMwareEndUserComputing]

Correct. If there is a valid refresh token, the application will make use of it to request a new access token. When refresh token is no longer valid, user has to login again.

[@bokunochannel84207]

question, where id_token would be stored?

[@bokunochannel84207]

how the client know, which user the id_token belongs to?

[@VMwareEndUserComputing]

I'm not a developer so I cannot really help with that level of knowledge..

[@pg4694]

u have explained very thing properly but can uu simply mentin the basic diff between between o auth and oidc with one real example

[@VMwareEndUserComputing]

OAuth is used for delegating access, i.e. allow an application to act on your behalf where OIDC is used to authenticate a user.

[@pg4694]

@@VMwareEndUserComputing thankyou so much

[@naheliegend5222]

that was a huge amount of information. I do no understand everything.

[@VMwareEndUserComputing]

Well, OAuth 2.0 and OIDC is much, much broader than what I covered in the video.. I hoped it would be a good introduction to the topic for a typical IT admin. What was it you did not understand? Have you watched the other recommended videos? E.g. the one on Identity and Access Management? It might provided the needed background.

[@storozhukua]

refresh token have to be in backEnd

[@gugafonseca3388]

Fantastic explanation. Thank you Peter!