Skip to content

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 17 Nov 16:25
· 44 commits to main since this release
71328cd

ISO mdoc support. No breaking changes: existing configuration, the management API and SD-JWT VC behaviour are unchanged. New policy settings and audit events are additions.

Added

  • ISO mdoc (mso_mdoc) presentations over OpenID4VP 1.0 and HAIP 1.0 (ADR-012, configuration):
    • issuer data authentication: the mobile security object, value digests, validity, and the IACA certificate rules for the mDL (country and state, extended and key usage, issuing_country and issuing_jurisdiction);
    • mdoc authentication by device signature over the OpenID4VP session transcript, with key authorizations for device-signed elements;
    • the DeviceResponse version and status rules;
    • DCQL [namespace, element] paths with intent_to_retain, and the age_over_NN rule (an age_over_21: true answers a request for age_over_18);
    • mso_mdoc in the request's vp_formats_supported;
    • revocation: the MSO's Token Status List reference is checked like an SD-JWT VC's status;
    • allowed_issuers names an mdoc issuer by its trust anchor's subject name or its trusted-list entity name, never by the document signer's name, which changes on rotation.
  • Conformance warnings: departures from ISO/IEC 18013-5 that the adapter tolerates are accepted and written to the audit trail as conformance_warning events. These are a P-384 device key, a document signer valid for more than 457 days or without a CRL distribution point, and a root certificate in the x5chain, which is ignored and never trusted. The policy setting mdoc_strict_conformance refuses P-384 device keys.
  • Token Status List in CWT form (draft-ietf-oauth-status-list-21), next to the JWT form. A token served by the eudi-dev wallet is a test fixture.
  • adapter-crypto-brainpool, an opt-in module for mdoc signatures on brainpool curves, with BouncyCastle. The service image carries it, off unless EUDIW_CRYPTO_BRAINPOOL=true.
  • A strict CBOR decoder and COSE_Sign1 verification in adapter-core, cross-checked in tests against Authlete cbor.
  • The Compose demo has the eudi-dev wallet present an mdoc PID end to end, and checks that one signed over another session transcript is rejected. CI runs both.

Not supported yet

  • Device MAC, which needs a reader key that the OpenID4VP flow does not have.
  • MSO status mechanisms other than a Token Status List reference. Under require_valid they are rejected.

Artifacts

  • Image: ghcr.io/su-engineering/eudiw-adapter:0.2.0 (sha256:8b6007e0de1f70cd232dca9c5052c1d36fb361b1ff72b8a04f3a8ae5e03368d1), linux/amd64 and linux/arm64, signed with cosign, SBOM and provenance attached
  • Chart: oci://ghcr.io/su-engineering/charts/eudiw-adapter --version 0.2.0, signed with cosign; also attached below
  • Web component: @su-engineering/eudiw-request@0.2.0, published with provenance

Verify the image: see docs/kubernetes.md.