Skip to content

WS_AP_MS_ProtocolMessages_037c

Objective

Verify that the Wallet sends a correct typ header of the Wallet Instance Attestation as Client Attestation, when using Pushed Authorization Requests for issuance.

References

  • [CIR 2024/2979 amended] annex Ib
  • [ETSI TS 119 472-3] section 4.4
  • [HAIP] section 4.3
  • [OpenID4VCI] section E
  • [RFC9126] section 2.1
  • [IETF draft-attestation-based-client-auth] section 5.1

Profile applicability

None

EUDI-wallet relevancy

EUDI_generic | EUDI_required

Technology

Issuance via Redirects.

Preconditions

  1. Wallet is set to 'default_configuration_1'
  2. End-user is engaging with a Credential Issuer using a User-agent.
  3. Wallet started engagement with Credential Issuer.
  4. Wallet successfully obtained Credential Issuer Metadata.
  5. Wallet send a HTTP POST Request for a Pushed Authorization Request to the PAR Endpoint of the selected Authorization Server.
  6. Wallet send a correctly signed and trusted Wallet Instance Attestation as a Client Attestation.
  7. Wallet send a syntactically correct header of the Wallet Instance Attestation as Client Attestation.

Test Scenario

  1. Verify the typ JOSE header of the Wallet Instance Attestation (i.e. in the JWT header).

Expected results

  1. The value of the typ header of the WIA has the value oauth-client-attestation+jwt.