liveBook · Manning

Wallet standard

As explained in Authorization in Action

A wallet standard specifies how digital credentials are stored, protected, and managed on a holder's device.

A wallet standard defines how digital credentials are stored, protected, and managed on a holder’s device. It forms one layer of a verifiable-credential ecosystem alongside issuance and presentation protocols, supporting authorization without determining the policy decision itself. section 16.7

Credential presentation flow

A wallet stores a signed credential. A policy enforcement point (PEP) requests attributes, the holder assembles a presentation, and the verifier checks issuer keys and signatures before a policy decision point (PDP) evaluates normalized claims. section 16.7

Implementations may use the W3C Verifiable Credentials Data Model with decentralized identifier (DID) resolution, or OpenID for Verifiable Credentials protocols that reuse OAuth and OpenID Connect conventions. section 16.7

How Authorization in Action covers it

How deep it goes
Defines storage, protection, and management responsibilities, then connects them to presentation and verification without detailing wallet implementation internals.
Examples
Uses signed credentials, holder-assembled presentations, issuer-key verification, and normalized claims evaluated by a policy decision point.
What you can do after
Evaluate how wallet handling fits into interoperable verifiable-credential authorization flows.
How it connects
Connects verifiable credentials with issuance protocols, presentation protocols, verifiers, policy enforcement points, policy decision points, DIDs, OAuth, and OpenID Connect.

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.