Watch and track your favorite playlist.
Curated by: Dedicated Managers (12 videos)
In this video discuss section 1.4 "Access Token" of the OAuth 2.0 Specification (IETF RFC 6749). https://tools.ietf.org/html/rfc6749#section-1.4 I discuss how access tokens are credentials that replace the usage of username and password. This allows a resource owner (usually a person) to allow a 3rd party to access a resource they own. I relate this back to the Google Drive example. I discuss how the access token is an abstraction layer (replacing username and password credentials) that allows for the resource owner to only allow certain access (scopes) their resources. I also discuss how having tokens makes the life of the resource server programmer easier in that the programmer only needs to implement an understanding of the tokens into the code, as opposed to having to write an entire set of code dedicated to authorizing the user. This video is part of a series: https://www.youtube.com/playlist?list=PLjuQOVlnQv2UUmUuq_ZuwFyVEXanuGh9v