Repository navigation
Verification in the browser over the W3C Digital Credentials API, transaction data, request-signing keys in HashiCorp Vault and AWS KMS, session status as Server-Sent Events, and a demo that needs no clone. A second wallet (walt.id) and the OpenID Foundation verifier test plan now run in CI. Existing configurations keep working; see Upgrading before a rolling upgrade.
Upgrading
- Digital Credentials API sessions need every pod on this version. Pods of earlier versions do not know mode
dc_api. MigrationV7widens the session mode check and adds a nullable column. - Transaction data needs every pod on this version. A pod of an earlier version neither sends nor checks
transaction_data, and its result has notransaction_data, which means no transaction was authorized. Replace all pods before clients send it. MigrationV6adds a nullable column.
Added
- OpenID4VP over the W3C Digital Credentials API: sessions with
mode: dc_apiand anoriginfrom the client's newdc_api_originsreturndc_api.requestfornavigator.credentials.get()(signed,x509_hash,expected_origins,dc_api.jwt); the client's backend relays the browser'sdatatoPOST /v1/verification-sessions/{id}/dc-api-response. SD-JWT VC is bound through the Key Binding JWTaudorigin:<origin>, mdoc through theOpenID4VPDCAPIHandovertranscript (ADR-017). CI runs it in headless Chromium against eudi-dev's DC API extension and wallet server (deploy/compose/dc-api/run.sh). <eudiw-request>mode="dc_api"withdc-api-requestanddc-api-url: a "use a wallet on this device" button that calls the Digital Credentials API and hands the response to your backend; eventeudiw-dc-api-error. The Node and Python examples offer it where the browser has the API, and relay the response (POST /verifications/{id}/dc-api).transaction_data(OpenID4VP 1.0): sessions can carry transactions, such as a payment, that the holder authorizes with the presentation. Policies allow types withtransaction_data_types; each entry names one SD-JWT VC credential query; the Key Binding JWT must carry the SHA-256 hash of every entry (transaction_data_mismatchotherwise), and the result returns the entries it carried. Never in status, events, webhooks or logs. ISO mdoc is refused for now. Tested with walt.id Wallet API 2 in CI (ADR-016).- A demo without cloning or building:
curl -fsSL https://raw.githubusercontent.com/su-engineering/eudiw-adapter/main/deploy/quickstart/run.sh | shruns the released image (pinned by digest, request-signing key in a file) with PostgreSQL, Keycloak and the eudi-dev wallet, and checks an SD-JWT VC, an untrusted issuer and an mdoc. CI'squickstartjob runs it. - Request-signing keys in AWS KMS:
verifier.aws_kmswithkey_idand optionalregionandendpoint. Credentials come from the AWS SDK's default chain (including EKS web identity). The newadapter-kms-awsmodule brings the AWS SDK (KMS, STS and the JDK HTTP client only, about 6 MB) into the service image (ADR-015). - Request-signing keys in HashiCorp Vault's Transit engine:
verifier.vault_transitwithaddress,key_name,token_fileand optionalmount,key_versionandnamespace. The token file is read on every signature and is not part of the configuration revision. Every signature, with any key source, is now checked against the request-signing certificate, so a key rotated in a key service fails closed; a signing failure is a503withRetry-Afterto the wallet (ADR-014). - walt.id Wallet API 2 also presents an ISO mdoc PID in the
demojob, so a second wallet now signs the OpenID4VP session transcript for mdoc. - CI runs the OpenID Foundation OID4VP 1.0 Final + HAIP verifier test plan on every change (
oidfjob). The job fails when any of the 14 modules ends differently frominterop/oidf/expected.jsonor the suite logs a failure or warning, and keeps the suite logs for 90 days.interop/oidf/ci.shruns the same thing on a laptop. Every module still ends in REVIEW; this is not certification. - A second independent wallet in CI: walt.id Wallet API 2 (1.2.1, pinned by digest) presents an SD-JWT VC to the Compose demo in the
demojob, a credential under a certificate chain the trusted list does not name is rejected, and a walt.id wallet that does not trust the demo relying-party root refuses the request.deploy/compose/waltid/run.shruns the same against a local demo. See the wallet table. - Session status as Server-Sent Events:
GET /v1/verification-sessions/{id}/events(scopeverification:read) sends the status view the poll returns, first the current one and then each change, and closes when the session is no longer pending. Never claims. The creation response carriesevents_url. Works across replicas through PostgreSQL. New settingsEUDIW_EVENTS_INTERVAL,EUDIW_EVENT_STREAMS_MAXandEUDIW_EVENT_STREAMS_PER_CLIENT, in the Helm chart asevents.interval,events.maxStreamsandevents.maxStreamsPerClient(ADR-013). Ingresses must not buffer the stream (Kubernetes notes).
Changed
- Bouncy Castle 1.87.
Artifacts
- Image:
ghcr.io/su-engineering/eudiw-adapter:0.3.0(sha256:4a181c771aa790d5623adca8e9cc3f28efa265313e83f9bd842f4123107f9c54), linux/amd64 and linux/arm64, signed with cosign, SBOM and provenance attached - Chart:
oci://ghcr.io/su-engineering/charts/eudiw-adapter --version 0.3.0, signed with cosign; also attached below - Web component:
@su-engineering/eudiw-request@0.3.0, published with provenance
Verify the image: see docs/kubernetes.md.