TokenRequestParameters

OID4VCI: Credential Issuers MAY support requesting authorization to issue a Credential using this parameter. The request parameter authorization_details defined in Section 2 of RFC9396 MUST be used to convey the details about the Credentials the Wallet wants to obtain.

CSC: OPTIONAL Arbitrary data from the signature application. It can be used to handle a transaction identifier or other application-spe cific data that may be useful for debugging purposes

RFC6749: REQUIRED, if the client is not authenticating with the authorization server.

RFC6749: REQUIRED. The authorization code received from the authorization server.

RFC7636: A cryptographically random string that is used to correlate the authorization request to the token request.

RFC6749: REQUIRED. Value MUST be set to authorization_code.

OID4VCI: The code representing the authorization to obtain Credentials of a certain type. This parameter MUST be present if grantType is urn:ietf:params:oauth:grant-type:pre-authorized_code.

RFC6749: REQUIRED, if the "redirect_uri" parameter was included in the authorization request, and their values MUST be identical.

RFC8707: When requesting a token, the client can indicate the desired target service(s) where it intends to use that token by way of the resource parameter and can indicate the desired scope of the requested token using the scope parameter.

RFC6749: OPTIONAL. The authorization and token endpoints allow the client to specify the scope of the access request using the "scope" request parameter. In turn, the authorization server uses the "scope" response parameter to inform the client of the scope of the access token issued.

OID4VCI: OPTIONAL. String value containing a Transaction Code. This value MUST be present if a tx_code object was present in the Credential Offer (including if the object was empty). This parameter MUST only be used if the grantType is urn:ietf:params:oauth:grant-type:pre-authorized_code.