| Steps | - 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" }
- Add response_mode attribute with value of query
- 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 pushed_authorization_request_endpoint specified within the discovery document
- Verify that the PAR endpoint returns an error of either invalid_request or invalid_request_object
|
|---|