Book Image

OAuth 2.0 Cookbook

By : Adolfo Eloy Nascimento
Book Image

OAuth 2.0 Cookbook

By: Adolfo Eloy Nascimento

Overview of this book

OAuth 2.0 is a standard protocol for authorization and focuses on client development simplicity while providing specific authorization flows for web applications, desktop applications, mobile phones, and so on. This book also provides useful recipes for solving real-life problems using Spring Security and creating Android applications. The book starts by presenting you how to interact with some public OAuth 2.0 protected APIs such as Facebook, LinkedIn and Google. You will also be able to implement your own OAuth 2.0 provider with Spring Security OAuth2. Next, the book will cover practical scenarios regarding some important OAuth 2.0 profiles such as Dynamic Client Registration, Token Introspection and how to revoke issued access tokens. You will then be introduced to the usage of JWT, OpenID Connect, and how to safely implement native mobile OAuth 2.0 Clients. By the end of this book, you will be able to ensure that both the server and client are protected against common vulnerabilities.
Table of Contents (16 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Index

Creating an Android OAuth 2.0 client using the embedded browser


Although there's a lot of vulnerabilities regarding the use of embedded browsers, they are still widely used and sometimes required in specific use cases. Before using embedded browsers, just be aware of the vulnerabilities described in RFC 8252 and make sure that you can't use in-app browser tabs as an alternative. For Android, you can use the Custom tabs feature that is described by the official documentation at https://developer.chrome.com/multidevice/android/customtabs. This recipe presents you with how to use embedded browsers (Android WebView) using the Implicit grant type just for brevity purposes.

Note

As an advice, useWebViewjudiciously because of issues mentioned in OAuth 2.0 for native apps specification (RFC 8252).

Remember to use the Authorization Code grant type if you are developing a production application.

Getting ready

To run this recipe you need the server application running on you environment. This is provided...