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

The ROPC grant flow

The ROPC flow moves the resource owner’s credential management into the client application. The resource owner is prompted directly by the client application, which usually has a form where the user can insert their credentials. For this reason, ROPC is not a recommended flow because it trusts that the client application will not misuse a user’s credentials.

The flow is described in the following diagram:

Figure 4.6 – ROPC grant flow

The diagram is explained in detail as follows:

  1. The resource owner directly inserts their credentials within the client application.
  2. The client application requests an access token directly to the /token endpoint of the authorization (AuthZ) server by sending the credentials the resource owner provided in the previous step. This is what a request looks like:
    POST /token?
    grant_type=PASSWORD
    &client_id=s6BhdRkqt3
    &scope=resource_server_id%20offline_access
    &username=userid1...