WS_AP_MS_ProtocolMessages_040b¶
Objective¶
Verify that the Wallet sends a correct Pushed Authorization Request, when authentication to a Authorization Server for requesting issuance of a Credential.
References¶
- [ETSI TS 119 472-3] section 4.4
- [HAIP] section 4.3
- [OpenID4VCI] section 5.1.2
Profile applicability¶
None
EUDI-wallet relevancy¶
EUDI_generic | EUDI_required
Technology¶
Issuance via Redirects.
Preconditions¶
- Wallet is set to 'default_configuration_1'
- End-user is engaging with a Credential Issuer using a User-agent.
- Wallet started engagement with Credential Issuer.
- Wallet successfully obtained Credential Issuer Metadata.
- Wallet send a valid and trusted PAR request the Authorization Server's PAR Endpoint.
- Wallet send a valid Authorization Request to the Authorization Server's Authorization Endpoint.
- Wallet send a syntactically correct Authorization Request Request Object.
Test Scenario¶
- Verify the
scopeparameter in the Pushed Authorization Request.
Expected results¶
-
The value of the
scopeparameter matches with one or more values, with whitespace(s) as separator, where each value matches ascopeof acredential_configurations_supportedof the Credential Issuer as stated in the Credential Issuer's metadata.- NOTE: this assumes the Credential Issuer's Metadata does include a unique
scopefor each supported Credential Configuration.
- NOTE: this assumes the Credential Issuer's Metadata does include a unique