liveBook · Manning

Authorization

As explained in Grokking Software Architecture

The process of determining whether an identity has permission to perform an action or access a resource.

A valet key can start a car without opening its glovebox. Authorization works the same way: it determines what an identity is allowed to do or access. Authentication answers a different question—who is the caller? section 11.3.2 section 9.7.1

The principle of least privilege keeps permissions as narrow as the job requires. A backend service that needs to read and write orders should have access to the Orders table, not the entire database. If the service is compromised, that restriction limits what an attacker can reach. section 9.7.1 section 11.10

OAuth 2.0 provides an authorization framework for delegated access; OpenID Connect (OIDC) handles authentication. An identity provider can manage identities and issue security tokens, so components can grant delegated access without transmitting the user's password. section 11.3.2

Table 11.1 Selecting the Correct OAuth 2.0 Flow by Architectural Scenario
Scenario
Recommended OAuth 2.0 Flow
Key Characteristic
Human User logging into a web or mobile app.
Authorization Code Flow (with PKCE)
Redirects the user to a secure login page hosted by the IdP.
Backend Service talking to another service (Machine-to-Machine).
Client Credentials Flow
No humans are involved; the service uses its own ID and Secret to obtain a token.

Compare the OAuth 2.0 flows recommended for a human user and for service-to-service access. section 11.3.2

Check the internal door

In a Zero Trust design, an Order Service presents its application token to a Customer Service. The receiving service validates the token and checks that the caller has the least privilege needed for the requested data. Being inside the network is not permission by itself. section 11.3.3

A service mesh can move shared communication duties into sidecar proxies, including mutual TLS and identity-based authorization. For service credentials, avoid hardcoded administrative credentials and static keys; retrieve short-lived tokens or runtime roles instead. section 11.3.3 section 9.7.1

How Grokking Software Architecture covers it

How deep it goes
Explains permission boundaries and flow selection with architectural examples, while stopping short of configuring complex cloud IAM policies.
Examples
Illustrates restricted access with a valet key, an Orders table, and a service presenting a token to another service.
What you can do after
Evaluate authorization boundaries and distinguish permission checks from identity verification.
How it connects
Connects authorization to authentication, least privilege, Zero Trust, identity providers, and service meshes.

Also explained in

Compare how 38 books explain authorization →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.