Request object, signed and/or encrypted JWT.
When used, it may contain all the properties below. Besides parameters
used by client authentication, all the other parameters should be inside
the request object.

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)

OAuth2.0 client identifier. Required when the client authentication method is using
"client_secret_post" or "tls_client_auth". It is optional when using "private_key_jwt"
client authentication; when specified it MUST match the "client_assertion" subject.

OAuth2.0 client secret. May be specified when using "client_secret_post" client
authentication method.

The "private_key_jwt" assertion being used to authenticate the client.

Type of the client assertion.

MTLS Client Certificate