oAuth and OpenID connect | Most confusing topic in plain english

oAuth 2 and OpenID Connect are the latest additions to OAuth 2.0, which was released in 2009. If you’re coming from the world of web forms, you may remember this as the OAuth 2.0 and OpenID Connect. oAuth 2.0 and OpenID Connect is a security enhancement to OAuth 2.0. It’s designed to prevent credential theft.

These are wonderful new technologies that allow websites to better connect to users when they access the site. For instance, when a user signs in to a website using their username and password, it is common that they will then be given a unique identifier that acts as the username when accessing the site. This unique identifier is called an OpenID.

Stay in touch:

[singarajusreedhar]

Best Explanation I ever seen on this topic. Thanks very much Sir!

[KalanaMahaarachchi]

Thanks for simple explanations. Lots of gray areas clarified

[madhavareddy]

I always was getting confused with this topic, but after watching this video things got clear, thanks a tons for your explanation and effort

[chetansn]

Great explanation with real time examples, should appreciate 🎉

[tsbatm]

Great content. Learning many things about coding. I'm new to programming, coming from financial field. Thinks you gave me most of fundamentals in short way. Thanks and wish you all the best.

[shrinidhiym]

Guru, I can name you Dinesh Sir. Even a non technical nerd can understand these concepts. Great explanation. Thank you :)

[sureshsurendran]

Nice Video. Simple explanation. Thanks 👍🏻

[manideepkumar]

u took wonderful question Why 2 steps why cant we get auth token directly instead of auth code? u answered

And this single step of getting directly token is for app to app / java service- micro service communications where there is not front-end and where we dont need user to provide consent i think only for that situation alone we should use client credentials grant type to get auth token directly
This is what i heard, but correct me if i am wrong

1) with oauth we can limit the access means as we are already doing authorization, was it not authentication?
because a user will be authorized to enter any building after successful authentication right?
so do we still need to bother about authentication after successful authorization?
still this a good video to understand clearly thanks for the attempt

[abdullatheef]

Very nice explanation. Appreciate your efforts

[ganesangceb]

much clear explanation, thank you so much

[Dhanasekarsvcse]

HI Krish,
Can you please also put videos related Microservice with Kafka .. thank you

[GlenBeach]

My takeaway, oAuth2 is for Authorization, while it uses OIDC for the authentication piece.

[parthibanakt]

Oauth explanation grt but Open ID Connect not getting clear idea how its differ from Oauth 2.0 can you demonstrate or differentiate for better understanding...!

[RamEchoes]

This is really an awesome explanation! Can you share any detailed document

[shivakumarhyd]

Are of improvement: Illustration should have had examples, as the same diagrams are plenty on net.

[rukshandevelopment]

Now only I understand why they send a Damn code instead of token in the first place.... 😃