Book Image

Mastering OAuth 2.0

Book Image

Mastering OAuth 2.0

Overview of this book

OAuth 2.0 is a powerful authentication and authorization framework that has been adopted as a standard in the technical community. Proper use of this protocol will enable your application to interact with the world's most popular service providers, allowing you to leverage their world-class technologies in your own application. Want to log your user in to your application with their Facebook account? Want to display an interactive Google Map in your application? How about posting an update to your user's LinkedIn feed? This is all achievable through the power of OAuth. With a focus on practicality and security, this book takes a detailed and hands-on approach to explaining the protocol, highlighting important pieces of information along the way. At the beginning, you will learn what OAuth is, how it works at a high level, and the steps involved in creating an application. After obtaining an overview of OAuth, you will move on to the second part of the book where you will learn the need for and importance of registering your application and types of supported workflows. You will discover more about the access token, how you can use it with your application, and how to refresh it after expiration. By the end of the book, you will know how to make your application architecture robust. You will explore the security considerations and effective methods to debug your applications using appropriate tools. You will also have a look at special considerations to integrate with OAuth service providers via native mobile applications. In addition, you will also come across support resources for OAuth and credentials grant.
Table of Contents (22 chapters)
Mastering OAuth 2.0
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
11
Tooling and Troubleshooting
Index

Hybrid architectures


Mobile applications come in many shapes and sizes. As such, the architecture of your mobile application can be flexible as well. There is no reason why your application has to use a single authorization workflow, as is described in the preceding section. If you have a mobile application, and a backend server, you can create a hybrid architecture to leverage the best of both worlds.

Implicit for mobile app, authorization code grant for backend server

Most service providers support the idea of having a single client use multiple authorization flows. For example, Facebook supports a single client application using both the implicit grant flow and the authorization code grant flow. We can leverage this capability and use the most appropriate flow for the given task. For instance, if your application requires some non-sensitive data in a read-only manner, this can be made directly from your native mobile application via the implicit grant flow. Your application may also require...