liveBook · Manning

Centralized namespace

As explained in Authorization in Action

A centralized namespace is a naming system maintained by one organization that ensures identifier uniqueness.

A centralized namespace is maintained by one organization that ensures identifier uniqueness within its authority. It is easy to implement, but its names are not easily portable. section 2.4.3

Centralized namespaces shape identity and authorization in several ways:

  • Provide stable identifiers for entities such as employees, supporting policies that require unambiguous and trustworthy names. section 2.4.3
  • Create dependency on the issuing organization; portability becomes difficult when identities move between authorities. section 2.4.3
  • Require careful lifecycle governance because reusing an identifier can redirect old policies, audit records, or entitlements to a different person. section 2.4.3

Employee numbers at ACME

An HR system assigns every employee a unique employee number and never reuses it. Reusing a departed employee’s number could cause an old entitlement or audit record to be associated with the wrong employee. section 2.4.3

How Authorization in Action covers it

How deep it goes
Defines the model, contrasts implementation ease with portability, and explains identifier-reuse failure without detailing implementation.
Examples
Uses usernames, employee ID numbers, and ACME employee-number assignment as examples.
What it assumes
Assumes basic identity and authorization concepts while explaining namespace effects through employee identifiers.
What you can do after
Evaluate centralized identifiers for uniqueness, portability, and lifecycle risks before relying on them in authorization.
How it connects
Connects namespace design with identity, authorization policies, identifiers, audit records, and entitlements.

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.