The HTTP method used for the OAuth transaction.

Select from the following values:

• POST

• GET

Enable/disable relay mode allows FortiADC to add an Authorization Header to the HTTP request after verifying the token.

Select from the following values:

• true

• false

• none

This enables applications to use incremental authorization to request access to additional scopes in context.

If you set this parameter's value to true and the authorization request is granted, then the new access token will also cover any scopes to which the user previously granted the application access.

A space-delimited, case-sensitive list of prompts to present the user. If you do not specify this parameter, the user will only be prompted the first time your project requests access.

Possible values are:

• disable — Disable prompts.

• none — Do not display any authentication or consent screens.

• consent — Prompt the user for consent.

• select_account — Prompt the user to select an account.

The amount of time in seconds the token will be valid. (Range: 120-86,400, default = 3600).

The client will not be allowed to access the scope after this time has elapsed.

Access to this URL will trigger a logout event. FortiADC will delete the cookie, so in the next access you will need to repeat the OAuth setup process.

A space-delimited list of scopes that identify the resources that your application could access on the user's behalf. These values inform the consent screen that the resource server displays to the user.

Scopes enable your application to only request access to the resources that it needs while also enabling users to control the amount of access that they grant to your application. This results in an inverse relationship between the number of scopes requested and the likelihood of obtaining user consent.