liveBook · Manning

Attribute query

As explained in Authorization in Action

An attribute query is a request identifying the claims or attributes needed from a holder for an access decision.

When an external person requests access, an attribute query asks for the specific claims needed to make that authorization decision—not for a particular credential. A policy enforcement point (PEP) derives the query from the applicable policy, and the holder’s wallet selects claims from one or more credentials. The result is a signed presentation containing only the required information. section 16.5

Figure 16.3 Claim-based credential presentation. Upon receiving an access request, the PEP requests the specific attributes it needs for the authorization decision. The holder’s wallet receives the attribute query, selects the necessary claims from one or more credentials, and assembles a signed presentation. The PEP verifies the presentation and prepares the claims for policy evaluation.

The flow shows the PEP requesting attributes, the wallet assembling a presentation, and the verification layer preparing claims for policy evaluation. section 16.5

An attribute query supports authorization that adapts to the request and business relationship:

  • Requests only relevant claims, such as an employer and certification status, rather than requiring a fixed credential. section 16.5
  • Combines claims from different credentials while preserving issuer binding and confirming that they belong to the holder’s wallet. section 16.5
  • Checks supplier employment and delegated contract authority before allowing access to a purchase order. section 16.8.1
  • Requests tenant, project, and role claims so policies can distinguish owners, contributors, reviewers, and finance approvers. section 16.8.4

How Authorization in Action covers it

How deep it goes
Explains query creation, wallet selection, signed presentation, verification, and policy evaluation, while deferring credential internals.
Examples
Uses employer and certification claims, supplier delegation, and project-role credentials as concrete authorization scenarios.
What it assumes
Assumes access requests, wallets, credentials, policy enforcement points, and policy decision points, while illustrating their interaction through scenarios.
What you can do after
Apply it via verifiable credential presentations to request minimal claims and supply normalized attributes for policy evaluation.
How it connects
Connects verifiable credentials, selective disclosure, policy enforcement points, policy decision points, and authorization.

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.