Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying OAuth 2.0 Cookbook
  • Table Of Contents Toc
  • Feedback & Rating feedback
OAuth 2.0 Cookbook

OAuth 2.0 Cookbook

By : Adolfo Eloy Nascimento
3.7 (3)
close
close
OAuth 2.0 Cookbook

OAuth 2.0 Cookbook

3.7 (3)
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 (9 chapters)
close
close

Creating an Android OAuth 2.0 client using the Implicit grant type with the system browser


The specification for OAuth 2.0, which is RFC 6749, address native mobile applications with just a small section. It does not states which grant type must be used or not, although it mentions the usage of Authorization Code and Implicit grant type. The only concern when using Implicit grant type is about that a refresh token is not returned requiring the authorization processes once the access token expires. Even though, the most recent specification, OAuth 2.0 for native apps (RFC 8252) states that implicit flow isn't recommended for native apps, basically because by using this grant type the client application will not be able to use PKCE, which avoids interception attacks (we will see more about PKCE in the Protecting an Android client with PKCE recipe).

Despite these considerations, this recipe still presents you with how to use the Implicit grant type, because depending on your scenario, you might...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
OAuth 2.0 Cookbook
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon