| Steps | These steps are conducted using the first Client registered to the Holder and occur using Client 1βs MTLS certificate.
- Retrieve Discovery Document and parse required endpoints
- Retrieve JWKS Key Set using jwks_uri attribute
- Validate JWKS keys are valid JSON, contain the required fields and are correctly encoded using unpadded base64url
- Verify all JWKS keys contain kids
- Verify all JWKS keys do not contain any private or symmetric keys
- Verify all JWKS keys are of at least 2048 bit in length
- Verify JWKS contains at least one key with alg of PS256 or ES256
- Create authorisation request with content of (roughly) similar to:
{
"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"
}
- Sign the authorisation request using PS256
- Create a client assertion containing iss, sub, jti, iat, exp, and aud
- Sign the client assertion using PS256
- Dispatch the authorisation request (8) using the client assertion (10) to the pushed_authorisation_request_endpoint specified within the discovery document
- Verify that the PAR endpoint returns HTTP Status 201 with a valid request_uri returned
- Verify that the content of the request uri meets entropy of at least 128-bits
- Initiate a browser initiation to the authorise endpoint specifying:
- request_uri retrieved in (12)
- client_id matching the iss of the authorisation request
- redirect_uri matching the authorisation request
- scope specifying scopes matching the authorisation request
- response_type of code id_token
- Deliberately fail out of browser consent initiation (i.e., force an error)
- Receive redirect request at the redirect_uri specified and extract the fragment content and verify the following:
- error is not present in the url query string (but is present in the fragment)
- Verify that the fragment does not contain code
- Verify that the fragment contains:
- error_description
- state
- error
- error_uri
- Verify that the fragment contains state and this matches the request object specified in (7)
- Verify that the error attribute is set to access_denied
|
|---|