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
About the Author
About the Reviewer
Customer Feedback


The last chapter presented you with how to create your own OAuth 2.0 Provider by implementing both the Authorization Server and Resource Server. All the interactions with the OAuth 2.0 Provider were made using direct requests through the CURL command-line tool. This chapter will show you how to create client applications using Spring Security OAuth2 and the RestTemplate interface. As this chapter is focused on client applications (that is, the third-party application that can be granted permissions by the Resource Owner), you will also see how to manage refresh tokens at the client side.


All recipes in this chapters does not use TLS/SSL when interacting with the OAuth Provider just for didactical purposes. When running in production, you must use TLS/SSL to protect every communication between the Client and the OAuth Provider.