Introduction

As the development of mobile applications increases, there is also an increase of API consumption, which needs to be performed securely. Native mobile applications are considered as public client types because of not being able to store confidential data as web applications. Because of the nature of native applications, the use of OAuth 2.0 might be hard to implement in a safe manner. In some cases, the most we can do is reduce the vulnerabilities or minimize the time window for an attack to be performed. The RFC 6749 by itself does not provide details on how to safely implement native mobile clients, which has been addressed by a recently published Request for Comments (RFC) at the time of writing, that is, RFC 8252—OAuth 2.0 for native apps.

This chapter will present you with how to implement native clients through an Android platform, using the grant types provided by OAuth 2.0 and some OAuth 2.0 profiles such as Proof Key for Code Exchange by OAuth Public Clients (PKCE) that...