miEUDIverifier.Core
1.2.0
See the version list below for details.
dotnet add package miEUDIverifier.Core --version 1.2.0
NuGet\Install-Package miEUDIverifier.Core -Version 1.2.0
<PackageReference Include="miEUDIverifier.Core" Version="1.2.0" />
<PackageVersion Include="miEUDIverifier.Core" Version="1.2.0" />
<PackageReference Include="miEUDIverifier.Core" />
paket add miEUDIverifier.Core --version 1.2.0
#r "nuget: miEUDIverifier.Core, 1.2.0"
#:package miEUDIverifier.Core@1.2.0
#addin nuget:?package=miEUDIverifier.Core&version=1.2.0
#tool nuget:?package=miEUDIverifier.Core&version=1.2.0
miEUDIverifier.Core
Reusable .NET 8 library to read EUDI Wallet PID identity data (family name, given name,
date of birth) via the EUDI Verifier Backend REST API (OpenID4VP). It builds the DCQL request,
polls for the wallet response and extracts the identity data — for both mso_mdoc
(ISO/IEC 18013-5) and SD-JWT VC (dc+sd-jwt) credential formats, including SD-JWT
disclosure parsing.
Part of the miEUDIverifier project (Apache-2.0), which also ships a ready-to-run web app with a browser UI, REST API and Docker image.
Install
dotnet add package miEUDIverifier.Core
Usage
// Program.cs — register via DI (reads the "VerifierSettings" configuration section)
builder.Services.AddMiEUDIverifier(builder.Configuration);
// Resolve the service and run a verification
var verifier = app.Services.GetRequiredService<VerifierApiService>();
var tx = await verifier.InitializeTransactionAsync();
var deepLink = tx.BuildWalletDeepLink(); // openid4vp:// deep link for the wallet
var qrPng = QrCodeService.GeneratePng(deepLink); // QR code as PNG bytes
var envelope = await verifier.WaitForWalletResponseAsync(tx.TransactionId);
var identity = await verifier.ExtractIdentityDataAsync(envelope);
// identity.FamilyName, identity.GivenName, identity.BirthDate, identity.CredentialFormat
Configuration (VerifierSettings section)
{
"VerifierSettings": {
"BackendUrl": "https://verifier-backend.eudiw.dev"
}
}
| Key | Default | Description |
|---|---|---|
BackendUrl |
https://verifier-backend.eudiw.dev |
Base URL of the EUDI verifier backend (the REST API — not verifier.eudiw.dev, which serves the demo UI) |
IntendedUseId |
TEST-01 |
Wallet-RP Intended Use id sent as intended_use_id. eudiw.dev requires one since August 2026; TEST-01 is its public test entry |
PollIntervalSeconds |
3 |
Polling interval for the wallet response |
PollTimeoutSeconds |
120 |
Maximum wait time for the wallet response |
Profile |
openid4vp |
OpenID4VP profile (openid4vp or haip) |
JarMode |
by_reference |
How the authorization request JWT is passed |
RequestUriMethod |
post |
HTTP method for request_uri |
ResponseMode |
direct_post |
Wallet response mode |
AuthorizationRequestScheme |
openid4vp |
URI scheme for the QR-code deep link |
IssuerChain |
(none) | PEM certificate chain of the trusted PID issuer |
SdJwtFormat |
dc+sd-jwt |
DCQL format id for the SD-JWT VC option |
SdJwtVctValues |
urn:eudi:pid:1, urn:eu.europa.ec.eudi:pid:1 |
Accepted vct values for the SD-JWT VC PID |
SessionTtlMinutes |
30 |
Time-to-live for verification sessions in hosting apps that manage parallel sessions (e.g. the miEUDIverifier web app / REST API) |
All values can be overridden via environment variables (e.g.
VerifierSettings__BackendUrl=…) or CLI arguments, following standard .NET configuration
binding.
What it requests
Only the PID credential with three attributes — family_name, given_name, birth_date —
offered to the wallet as either mso_mdoc or dc+sd-jwt (DCQL credential_sets options).
The DCQL query is built in VerifierApiService.InitializeTransactionAsync and can easily be
extended with more attributes or credential types.
License
Apache-2.0 — Copyright © Wolfgang Mitterbucher.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net8.0
- Microsoft.Extensions.Configuration.Abstractions (>= 8.0.0)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 8.0.0)
- Microsoft.Extensions.Http (>= 8.0.0)
- Microsoft.Extensions.Logging.Abstractions (>= 8.0.0)
- Microsoft.Extensions.Options (>= 8.0.0)
- QRCoder (>= 1.6.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
1.2.0 — Fixes two defaults that made the library unusable out of the box.
BackendUrl now points at https://verifier-backend.eudiw.dev/ (the REST API). It previously
defaulted to https://verifier.eudiw.dev/, which serves the Angular demo UI and answers the API
paths with 405.
New VerifierSettings.IntendedUseId (scalar, default "TEST-01") is sent as intended_use_id when a
transaction carries none of its own — mirroring how ResponseMode backs ResponseModes. Since August
2026 eudiw.dev rejects any request without one (MissingRegistrationCertificate); TEST-01 is the
public test intended use it publishes at GET /ui/intended-uses. A per-backend IntendedUseIds entry
still wins; set IntendedUseId to "" when pointing at a backend of your own.
Both defaults only apply where nothing is configured, so existing configuration is unaffected.
1.1.0 — Multi-backend support: serve several trust ecosystems from one app.
Added VerifierSettings.Backends / DefaultBackend / MdocOnlyBackends / IntendedUseIds /
ResponseModes, the TransactionOptions type, intended_use_id on the init request, and the
German EUDI Wallet (Bundesdruckerei prototype) PID as a further SD-JWT VC option.
Note: InitializeTransactionAsync gained an optional TransactionOptions parameter ahead of
the CancellationToken. Calls passing the token by name or omitting it are unaffected;
positional InitializeTransactionAsync(ct) calls must be updated to (null, ct).