Join our Newsletter — 33% off our NHI Course

Could EUDI wallets change verifier identity governance?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: EUDI wallet adoption puts verifier identity at the center of enterprise identity design, with Curity saying the wallet must trust the party asking for attributes. OAuth 2.0 still handles authorization, so token issuance and API policy stay inside the enterprise boundary.

Editorial analysis by NHI Mgmt Group, based on content published by Curity: “EUDI Wallets: Enterprise Takeaways from DICE 2026”.

Key questions

Q: Why do EUDI wallets not replace OAuth 2.0 for enterprise access control?

A: Wallets can authenticate a user or prove attributes, but they do not issue the enterprise access token that protects APIs.

Q: What are the main governance risks in wallet-based identity flows?

A: The main risks are weak issuer trust, poor revocation handling, inconsistent assurance levels, and unclear consent records.

Q: How should security teams govern verifier identity in EUDI wallet flows?

A: Treat the verifier as a registered trust anchor, not just an application endpoint.

Practitioner guidance

  • Define the verifier trust model Inventory every service that will ask wallets for attributes, then decide how each verifier is identified, registered, and authorised to request data.
  • Keep OAuth 2.0 as the authorization layer Use wallet credentials for authentication and claims intake, but continue to mint and govern enterprise access tokens inside your authorization server.
  • Separate attribute presentation from API access Do not map wallet attributes directly to resource access.

Bottom line: EUDI wallets move the verifier role into the centre of enterprise identity design, because the wallet must trust the party asking for attributes.

Glossary terms: Verifier Identity, Selective Disclosure, Wallet-Ready Authorization, Attribute-Based Identity Verification

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Verifier identity is becoming the new trust boundary in wallet ecosystems: the hard problem is no longer only whether a user can present a valid credential, but whether the relying party itself can be trusted by the wallet. That shifts governance from user onboarding alone to verifier registration, purpose declaration, and cryptographic identity assurance. Practitioners should treat verifier trust as a first-class identity control, not an integration detail.

A question worth separating out:

Q: How should IAM teams handle privacy when wallets use distinct identifiers per verifier?

A: They should stop assuming that the same user identifier will be available across services. Instead, they need attribute-based governance, minimal logging, and carefully designed correlation rules that do not depend on persistent cross-service tracking.

👉 Read our full editorial: Eudi wallets and oauth 2.0: what verifiers must change



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.