Skip to main content

FAPI-RW-ID2-ENSURE-AUTHORISATION-REQUEST-MISSING-REQUEST-FAILS

NameEnsures the holder rejects requests where a request object or request uri is not supplied
CategoryINFOSEC
Execution MethodAUTOMATED (FAPI BASELINE)
Preconditions
DescriptionThis test calls the authorization endpoint without using a request object (i.e. with all the parameters passed in the url query), and should end with the authorization server showing an error message that the request is invalid (a screenshot of which should be uploaded) or with the user being redirected back to the conformance suite with an invalid_request error.
Steps

Client 1 Initiation
These steps are conducted using the first Client registered to the Holder and occur using Client 1’s MTLS certificate.

  1. Retrieve Discovery Document and parse required endpoints
  2. Retrieve JWKS Key Set using jwks_uri attribute
  3. Validate JWKS keys are valid JSON, contain the required fields and are correctly encoded using unpadded base64url
  4. Verify all JWKS keys contain kids
  5. Verify all JWKS keys do not contain any private or symmetric keys
  6. Verify all JWKS keys are of at least 2048 bit in length
  7. Verify JWKS contains at least one key with alg of PS256 or ES256
  8. Create a client assertion containing iss, sub, jti , iat, exp and aud
  9. Sign the client assertion using PS256
  10. Initiate a browser initiation to the authorize endpoint specifying:
    • client_id matching the iss of the authorisation request
    • redirect_uri matching the registered redirect uri
    • scope specifying scopes
    • claims containing a urlencoded json of claims objects
    • state containing a state value
    • nonce containing a nonce
    • response_type of code id_token
  11. Holder should reject the request by either:
    • Showing an error page to the browser
    • Redirecting back to the Recipient, provided the supplied redirect_uri matches one of those registered, with an oauth2 invalid_request error
Inputs
Expected ResultsThe Holder must reject requests which do not contain their parameters in signed request objects