RP_WS_SM_SessionEncryption_005b_UF

Objective

Verify that the Relying Party rejects an Authorization Response via the W3C Digital Credentials API encrypted to the ephemeral key of another transaction.

References

• [HAIP] section 5, 5.2
• [OpenID4VP] section 8.3, A.4
• [ARF] Annex 2, OIA_08, OIA_08a
• [CIR 2024/2982 amended] Annex II

Profile applicability

• Relying Party supports presentations via the W3C Digital Credentials API.

EUDI-wallet relevancy

EUDI_generic | EUDI_required

Technology

• Presentation via the W3C Digital Credentials API with response mode dc_api.jwt.

Preconditions

1. The Relying Party is set to default_configuration_rp_1.
2. The test environment publishes default_trust_configuration_rp, and the Relying Party has loaded it.
3. Test case RP_WS_IA_MainInteraction_001a or RP_WS_IA_MainInteraction_001b passed in the same environment for the presentation flow of this test case.

Test Scenario

1. Start a presentation for default_query_pid via the W3C Digital Credentials API (transaction T1) and record the encryption key from the client_metadata of its request. Send no response for T1.
2. Perform a presentation for default_query_pid via the W3C Digital Credentials API (transaction T2) in which the Conformance Wallet encrypts an otherwise valid Authorization Response for T2 to the encryption key recorded for T1, with the kid of that key.

Expected results

1. The request of T1 carries an encryption key in its client_metadata.
2. The Relying Party rejects the presentation: its verification result reports a failure and releases no attribute value from the presentation, and the endpoint receiving the Authorization Response does not answer with HTTP status 5xx.

Comments

The credential format does not affect this test case; use default_credential_pid in a format the Relying Party requests.