Urgent.News

What's breaking now, across thousands of outlets.

Tech

Digital Credentials API shifts the prompt, not the verification burden

Digital Credentials API shifts the prompt, not the verification burden A browser-mediated credential prompt can make a wallet flow easier to use. The web page asks the user agent for a digital credential, the user selects a wallet or credential, and the selected protocol carries a request and response. The visible prompt belongs to the browser. The trust decision still belongs to the relying…

The W3C Digital Credentials API aims to simplify the process of requesting digital credentials through a browser-mediated prompt. This prompt, visible to the user, is handled by the browser, not the relying party, allowing for a streamlined wallet flow. The API is designed to be format-neutral and protocol-neutral, enabling it to work with various credential formats such as OpenID Verifiable Presentations.

However, this neutrality also means that the request and response objects can carry protocol-specific fields that a general browser interface may not validate.

For a credential to be accepted, it must be bound to the intended verifier, session, and transaction using a nonce or equivalent challenge. This nonce should be unpredictable, single-use, and checked against a server-side record to prevent reuse and ensure its uniqueness. Despite the browser displaying the initiating site, the application still needs to compare this origin with its own allowlist and session state to validate the request.

The response also requires a policy defining the credential format, issuer, proof type, holder binding, status mechanism, and disclosed attributes. A valid signature proves only that a key signed some bytes, not that the issuer is trusted for the specific request or that the credential was valid at the time of presentation. Browser mediation enhances transparency, but it does not replace the need for server-side trust decisions regarding issuers and transaction matches.

Applications should request only the necessary attributes and clearly display the purpose of the request in their interface. It is crucial for verifiers to log presentation as a transaction event without storing excess credential data. Deployment controls, such as maintaining an allowlist of supported wallet protocols and credential formats, are essential. Rejecting unknown protocol identifiers and malformed request objects before they reach a wallet, and using TLS to secure the response endpoint, are also vital measures.

To ensure robust security, tests should be conducted to check for replay attacks, wrong origins, expired statuses, unknown issuers, altered disclosed attributes, and responses after the session expires. The verifier policy version and evidence used for each decision should be recorded. While the browser prompt is a significant part of the flow, it is not the security boundary that determines credential trustworthiness.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Navigation 3: You Own the Back Stack Now. Here’s How Not to Leak It

Navigation 3 hands you the back stack as plain state. There is no controller to ask, no graph to inflate, no hidden NavBackStackEntry lifecycle you can only observe.

  • Navigation 3 provides direct access to back stack as plain state
  • Developers must manage one entry per destination, cleanup, restoration
  • Nav3 consists of keys (compact, immutable) and NavDisplay (UI conversion)

More from Tuesday 17 November →