OAuth explained OAuth 2.0

OAuth explained OAuth 2.0

HomeJan GoebelOAuth explained OAuth 2.0
OAuth explained OAuth 2.0
ChannelPublish DateThumbnail & View CountDownload Video
Channel AvatarPublish Date not found Thumbnail
0 Views
More exclusive content: https://productioncoder.com/you-decide-what-we-build-next
Twitter: https://twitter.com/_jgoebel
Website: https://jangoebel.com
Blog: https://productioncoder.com

00:00 What is OAuth and what problem does it solve?
01:07 OAuth Authorization Server
02:09 OAuth scopes
03:13 OAuth authorization types
04:05 OAuth for service accounts (two-legged OAuth)
06:06 Two-legged OAuth
07:00 OAuth is an authorization framework

In this video, we explain the concepts behind OAuth (Open Authorization), which allows third-party applications to gain limited access to APIs either on behalf of a person or on their own behalf. We explain why OAuth exists and how OAuth ensures that usernames and passwords do not need to be shared with third-party applications.

OAuth allows you to request access tokens from an authorization server so that you can access an API (resource server) on behalf of the resource owner. To obtain the token, you must log in to the authorization server. There are several ways a third-party application can obtain an access token – called grant types. A grant type is a way a third-party application can obtain access tokens. OAuth provides a variety of grant types such as authorization code flow, device code flow, client credential flow, and password flow. The implicit flow and password grant are no longer recommended by the OAuth Working Group.

Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.