Book Image

Cloud Identity Patterns and Strategies

By : Giuseppe Di Federico, Fabrizio Barcaroli
5 (1)
Book Image

Cloud Identity Patterns and Strategies

5 (1)
By: Giuseppe Di Federico, Fabrizio Barcaroli

Overview of this book

Identity is paramount for every architecture design, making it crucial for enterprise and solutions architects to understand the benefits and pitfalls of implementing identity patterns. However, information on cloud identity patterns is generally scattered across different sources and rarely approached from an architect’s perspective, and this is what Cloud Identity Patterns and Strategies aims to solve, empowering solutions architects to take an active part in implementing identity solutions. Throughout this book, you’ll cover various theoretical topics along with practical examples that follow the implementation of a standard de facto identity provider (IdP) in an enterprise, such as Azure Active Directory. As you progress through the chapters, you’ll explore the different factors that contribute to an enterprise's current status quo around identities and harness modern authentication approaches to meet specific requirements of an enterprise. You’ll also be able to make sense of how modern application designs are impacted by the company’s choices and move on to recognize how a healthy organization tackles identity and critical tasks that the development teams pivot on. By the end of this book, you’ll be able to breeze through creating portable, robust, and reliable applications that can interact with each other.
Table of Contents (15 chapters)
1
Part 1: Impact of Digital Transformation
4
Part 2: OAuth Implementation and Patterns
8
Part 3: Real-World Scenarios

Native applications

A native application, as already explained, is a non-web application (by non-web application, we mean something that is not supposed to be browser-based, but still uses the REST or SOAP protocols for client-server interaction) written for a specific operating system that runs side by side with other applications on that operating system. Nowadays, native applications run mostly on mobile platforms such as iOS and Android, but it is very common to encounter native applications running on Windows as Win32 and Store applications, among other things.

It’s rare to find a native application that does not interact with external APIs to implement its business logic and therefore, it’s also common that these applications require an access token to securely communicate with such external services.

As we will appreciate in the rest of this chapter, native applications have many similarities to SPAs. This is because both of them interact with APIs located...