| Steps | - Retrieve Discovery Document and parse required endpoints
- Retrieve JWKS Key Set using jwksuri 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": {
"sharingduration": 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 (9) using the client assertion (11) to the pushedauthorizationrequestendpoint specified within the discovery document
- Verify that the PAR endpoint returns HTTP Status 201 with a valid requesturi returned
- Verify that the content of the request uri meets entropy of at least 128-bits
- Initiate a browser initiation to the authorize endpoint specifying:
- requesturi retrieved in (13)
- clientid matching the iss of the authorisation request
- redirecturi matching the authorisation request
- scope specifying scopes matching the authorisation request
- responsetype of code idtoken
- Proceed through authorisation flow within the browser
- Receive redirect request at the redirecturi specified and extract the fragment content and verify the following:
- state is not present in the url query string (but is present in the fragment)
- Verify that the fragment contained in the redirect response contains only:
- Verify that code is of sufficient length and has at least 128-bit entropy
- Decrypt idtoken using encryption key for client and verify signature
- Validate the idtoken by verifying iss, aud, exp, iat, authtime, acr, sub and nbf claims
- Verify nonce within decrypted idtoken matches nonce specified in (8)
- Verify acr returned matches the one request (normally urn:cds.au:cdr:2)
- Extract shash and chash from ID Token
- Verify chash is correctly validated against specified code
- Verify shash is correctly validated against specified state
- Create a client assertion for submission to the token endpoint
- Perform POST /token using generated client assertion from (27), granttype of authorizationcode, code retrieved in (18) and redirecturi specified in (15)
- The response should contain a valid set of tokens
- Wait 1 second
- Attempt to execute (27)-(29) again, if the request succeeds this test case is a warning state. If it fails with an invalidgrant error it is a success.
- Wait 30 seconds
- Attempt to execute (27)-(29) again, if the request succeeds this test case is a failure state. If it fails with an invalidgrant error it is a success.
|
|---|