liveBook · Manning

Namespace management

As explained in Authorization in Action

Namespace design is the specification of how names are structured, assigned, scoped, and resolved within an identity system.

Namespace management specifies how names are structured, assigned, scoped, and resolved so identifiers remain stable, unambiguous, discoverable, and trustworthy. These properties directly affect authorization: unclear boundaries can cause policies to confuse employees, contractors, customers, and service accounts. section 2.4.3

Common namespace structures include:

  • Centralized namespaces assign unique identifiers through one organization. They are easy to implement but can become nonportable and brittle when tied to one authority. section 2.4.3
  • Hierarchical namespaces organize names beneath a known root. They support discovery and allow local control without creating collisions; DNS, X.509 certificates, and LDAP are examples. section 2.4.3

Employee identifiers

An HR system might assign every employee a unique employee number and never reuse it. Reusing a former employee’s number could attach old policies, audit records, or entitlements to a different person. section 2.4.3

How Authorization in Action covers it

How deep it goes
Explains namespace properties, classifies centralized and hierarchical structures, and contrasts implementation, portability, discovery, and collision tradeoffs.
Examples
Uses employee numbers, HR assignment, LDAP paths, DNS, X.509 certificates, and organizational identity categories as examples.
What you can do after
Evaluate namespace choices and identify identifier designs that could produce incorrect authorization decisions.
How it connects
Connects identity namespaces with authorization policies, identifier uniqueness, discovery, LDAP, DNS, and X.509 certificates.

Related concepts

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