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)
Part 1: Impact of Digital Transformation
Part 2: OAuth Implementation and Patterns
Part 3: Real-World Scenarios

Web applications

In this section, we refer to a web application as a multi-page application to distinguish it from the SPA discussed later in this chapter.

When we use the term multi-page application, we refer to the traditional web application backed by a web server. A user accesses a multi-page application through a web browser (see the previous definition of user agent), which interacts with the web server by exchanging and requesting data – the web server typically responds to browser requests (HTTP requests) by computing a new page and sending it back to the browser for user visualization and further interaction.

We can think of a typical web application as a set of layers. The set of layers is defined according to the framework used – for example, Model-View-Controller (MVC), Model-View-Adapter (MVA), or Presentation-Abstraction-Control (PAC). Regardless of the framework used, we can increase the level of abstraction (without going into detail) and think of...