FAPI-RW-ID2-ENSURE-DIFFERENT-NONCE
| Name | Verifies behaviour related to supplying a nonce on an endpoint different to a request |
|---|---|
| Category | INFOSEC |
| Execution Method | AUTOMATED (FAPI BASELINE) |
| Preconditions | |
| Description | This test passes a different nonce in the authorization_endpoint parameters to the one inside the signed request object. The authorization server must either return an invalid_request error back to the client, and must show an error page (saying the request object is invalid as the 'nonce' value in the request object and outside it are different - upload a screenshot of the error page), or must successfully authenticate and return the nonce from inside the request object in the id_token. |
| Steps |
{
"aud": "https://localmachine:8103/local-conformance-holder",
"scope": "openid profile bank:accounts.basic:read bank:accounts.detail:read",
"claims": {
"sharing_duration": 7776000,
"id_token": {
"acr": {
"value": "urn:cds.au:cdr:2",
"essential": true
}
}
},
"iss": "4unxLnjKSMQCTRYU1X1Bed",
"response_type": "code id_token",
"redirect_uri": "https://localhost.emobix.co.uk:8443/test/a/wikkitgate/callback",
"state": "LwI4CZHGDm",
"exp": 1603332124,
"nonce": "vVqWbuseiL",
"client_id": "4unxLnjKSMQCTRYU1X1Bed"
} |
| Inputs | |
| Expected Results | The Holder must either complain about mismatched nonce's or ignore the nonce specified in the authorisation request query string |