WS_AP_IA_Supportive_011a¶
Objective¶
Verify that the Wallet can handle an correct response when submitting a Pushed Authorization Request (PAR) to the Authorization Server's Pushed Authentication Request Endpoint.
References¶
- [ETSI TS 119 472-3] section 4.1
- [HAIP] section 4
- [OpenID4VCI] section 5.1.4
- [RFC9126] section 2
Profile applicability¶
None
EUDI-wallet relevancy¶
EUDI_generic | EUDI_required
Technology¶
Issuance via Redirects. Credential Issuance using the Authorization Code Flow.
Preconditions¶
- Wallet is set to 'default_configuration_1'.
- Wallet started engagement with Credential Issuer.
- Wallet successfully obtained Credential Issuer Metadata.
- Wallet successfully obtained the Authorization Server Metadata, including
pushed_authorization_request_endpoint. - The Wallet sent a valid Pushed Authorization Request to the Authorization Server's Pushed Authorization Request Endpoint.
Test Scenario¶
- Issuer responds with a valid PAR Response. That is a HTTP Response:
- with a HTTP Header
Content-Typewith valueapplication/json, containing: - with the HTTP Response Body in JSON format:
- contains a
request_uri - contains a
expires_in
- contains a
- with a HTTP Header
Expected results¶
- The subsequent Authorization Request sent through the User-agent contains the exact
request_urivalue returned by the Authorization Server.