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

Hybrid flows

Hybrid flows (part of the OIDC specification) mix authorization code grant and implicit flows together, enabling the issuing of access tokens and ID tokens at different phases compared to when those flows are used alone.

During the first call to the /authorize endpoint of the authorization server, a client application can specify the following values for the response_type parameter, making the authorization server behave differently:

  • code token: When specified in the HTTP request, an access token and an authorization code must be included in a successful response
  • code id_token: When specified in the HTTP request, an authorization code and an ID token must be included in a successful response
  • id_token token: When specified in the HTTP request, an ID token and an access token must be included in a successful response
  • code id_token token: When specified in the HTTP request, an access token and an ID token must be included in a successful response
  • ...