v151 · identity · deprecation

Protocol filtering in Digital Credential API

The Digital Credentials API used to be an opaque pipe for any exchange protocol. Chrome 151 starts a developer trial for deprecating unspecified protocols, while DigitalCredential.userAgentAllowsProtocol() reports which protocol identifiers the browser allows. ChromeStatus schedules removal of the arbitrary pipeline for Chrome 160, but still labels the feature “Proposed.”

concepts

  1. Protocol allowlist checker

    Call the real DigitalCredential.userAgentAllowsProtocol() for each protocol in the current Editor’s Draft and for any string you type. A rejected sentinel can indicate that filtering is active; each result reports browser policy, not wallet, credential, or OS support.

    interactive

  2. Compliant request builder

    Assemble a navigator.credentials.get({ digital: { requests } }) call, pre-flight each protocol with userAgentAllowsProtocol(), and optionally fire the real request to see how the browser responds.

    interactive

  3. Deprecation & migration guide

    Compare a protocol identifier with the current Editor’s Draft table and the proposed Chrome 151→160 deprecation plan, then inspect separate presentation and issuance migration patterns.

    interactive

why the pipeline narrows

The Digital Credentials API was originally designed as an opaque transport for arbitrary exchange protocols. In November 2025 the FedID Working Group resolved to normatively reference a bounded set, so specifications and browsers can reason about the protocols being brokered. The current Editor’s Draft lists OpenID4VP variants and ISO mdoc for presentation, and OpenID4VCI for issuance. ChromeStatus records a developer trial from Chrome 151 and schedules removal of the arbitrary pipeline for Chrome 160, while the overall Chrome status remains “Proposed” (updated 2026-06-18). Filtering narrows protocol identifiers; it does not by itself verify request data, the verifier, a wallet, an available credential, user consent, or successful disclosure.

references

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗