Request object, signed and/or encrypted JWT.
When used, it may contain all the properties below. For FAPI, besides parameters
used by client authentication, all the other parameters should be inside
the request object. Based on OIDC specification, it is possible to have
the same parameters inside and outside request object, but the one inside the
request object will supercede the one outside.

A URI pointing to request object. Upon receiving this, the OIDC Provider is
expected to fetch the request object first. In the case of Pushed Authorize
scenario, the request_uri points to a location known by OIDC Provider.

OAuth 2.0 Client identifier

OAuth 2.0 response_type value that determines the
authorization processing flow to be used

Mechanism to be used for returning parameters from the Authorization Endpoint

Redirection URI to which the response will be sent. This URI MUST
exactly match one of the Redirection URI values for the Client
pre-registered at the OIDC Provider

A space-separated string that specifies the requested Authentication Context
Class Reference values, with the values appearing in order of preference.

Opaque value used to maintain state between the request and the callback.

Value used to associate a Client session with an ID Token to mitigate replay attacks

Space-delimited string that specifies whether the Authorization Server
prompts the End-User for reauthentication and consent.

Code challenge used as proof for code exchange

Method used to calculate the code challenge

Space-delimited string indicating the OAuth 2.0 scope requested.
OpenID Connect requests MUST contain the openid scope value.

JSON string that contains individual claims requested.

Hint to the Authorization Server about the login identifier the End-User might
use to log in (if necessary)