Skip to content

Make A128GCM and A256GCM mandatory for the verifier, make either mandatory for the wallet #343

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jogu merged 5 commits into from
Nov 20, 2025
Merged

Make A128GCM and A256GCM mandatory for the verifier, make either mandatory for the wallet #343

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
88a20a8
fix: make a256gcm and a128gcm mandatory for verifiers, while making e…
awoie Nov 18, 2025
635cb04
fix: lang fix
awoie Nov 18, 2025
4b8ed40
Applied WG consensus
awoie Nov 18, 2025
23cf802
Applied editorial suggestion
awoie Nov 20, 2025
dd15b3b
Merge branch 'main' into awoie/fix-329
jogu Nov 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion openid4vc-high-assurance-interoperability-profile-1_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -257,7 +257,7 @@ The following requirements apply to OpenID for Verifiable Presentations, irrespe
* The DCQL query and response MUST be used as defined in Section 6 of [@!OIDF.OID4VP].
* Response encryption MUST be performed as specified in [@!OIDF.OID4VP, section 8.3]. The JWE `alg` (algorithm) header parameter (see [@!RFC7516, section 4.1.1])
value `ECDH-ES` (as defined in [@!RFC7518, section 4.6]), with key agreement utilizing keys on the `P-256` curve (see [@!RFC7518, section 6.2.1.1]) MUST be supported.
The JWE `enc` (encryption algorithm) header parameter (see [@!RFC7516, section 4.1.2]) value `A128GCM` (as defined in [@!RFC7518, section 5.3]) MUST be supported.
The JWE `enc` (encryption algorithm) header parameter (see [@!RFC7516, section 4.1.2]) values `A128GCM` and `A256GCM` (as defined in [@!RFC7518, section 5.3]) MUST be supported by Verifiers. Wallets MUST support `A128GCM` or `A256GCM`, or both. If both are supported, the Wallet SHOULD use `A256GCM` for the JWE `enc`. Verifiers MUST list both `A128GCM` and `A256GCM` in `encrypted_response_enc_values_supported` in their client metadata.
* Verifiers MUST supply ephemeral encryption public keys specific to each Authorization Request passed via client metadata as specified in Section 8.3 of [@!OIDF.OID4VP].
* The Authority Key Identifier (`aki`)-based Trusted Authority Query (`trusted_authorities`) for DCQL, as defined in section 6.1.1.1 of [@!OIDF.OID4VP], MUST be supported. Note that the Authority Key Identifiers mechanism can be used to support multiple X.509-based trust mechanisms, such as ISO mDL VICAL (as introduced in [@ISO.18013-5]) or ETSI Trusted Lists [@ETSI.TL]. This is achieved by collecting the relevant X.509 certificates for the trusted Issuers and including the encoded Key Identifiers from the certificates in the `aki` array .

Expand Down Expand Up @@ -723,6 +723,7 @@ The technology described in this specification was made available from contribut
* clarify that DCQL applies in HAIP as defined in OpenID4VP and all REQUIRED and OPTIONAL requirements remain the same
* add reference to ECCG Agreed Cryptographic Mechanisms 2.0
* require x5c header in the OID4VCI Appendix D key attestation
* require A256GCM and A128GCM for verifiers
* add "Non-normative Examples of Ecosystem-specific Extensions of this Specification" section

-05
Expand Down