liveBook · Manning

OpenID4VC

As explained in Authorization in Action

OpenID4VC is a family of OpenID specifications for issuing and presenting verifiable credentials using web identity infrastructure.

OpenID4VC is a family of OpenID specifications for issuing and presenting verifiable credentials through familiar web identity infrastructure. OpenID4VCI handles issuance, while OpenID4VP handles presentation. section 16.7

An OpenID4VC authorization flow typically connects:

  • A policy enforcement point (PEP) requests required attributes. section 16.7
  • A holder assembles and presents credentials through an OpenID4VP flow. section 16.7
  • The PEP verifies issuer trust, expiration, and revocation before passing normalized claims to the policy decision point (PDP). section 16.7

Interoperable authorization

A verifier can accept presentations delivered through different protocols while applying the same authorization checks: trusted issuers, expiration, revocation, and normalized attributes. The PDP evaluates attributes rather than the protocol used to issue or present the credential. section 16.7

How Authorization in Action covers it

How deep it goes
Connects discovery, transport, authentication, presentation, and claim evaluation but defers deeper treatment of DID-based identity.
Examples
Uses OpenID4VCI issuance, OpenID4VP presentation, signed claims, issuer keys, expiration, and revocation checks.
What it assumes
Assumes familiarity with authorization components and introduces OpenID4VC through PEP, holder, and PDP interactions.
What you can do after
Apply OpenID4VC flows while keeping credential verification consistent across supported delivery protocols.
How it connects
Ties OpenID4VC to verifiable credentials, OAuth, OpenID Connect, PEPs, PDPs, and issuer trust stores.

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.