import { DeviceVerificationResponse } from "https://deno.land/x/authlete_deno@v1.2.9/mod.ts";
Enums
The next action that the service implementation should take. |
import { DeviceVerificationResponse } from "https://deno.land/x/authlete_deno@v1.2.9/mod.ts";
Response from Authlete /device/verification API.
Properties
The authorization details. This represents the value of the
authorization_details request parameter which is defined in
"OAuth 2.0 Rich Authorization Requests".
The flag which indicates whether the client ID alias was used in the device authorization request for the user code.
The names of the claims which were requested indirectly via some special scopes. See 5.4. Requesting Claims using Scope Values in OpenID Connect Core 1.0 for details.
This property has null if the scope request parameter of the
device authorization request does not include the openid scope
even if special scopes (such as profile) are included in the
request (unless the openid scope is included in the default set
of scopes which is used when the scope request parameter is omitted).
The dynamic scopes which the client application requested by the
scope request parameter. See the description of DynamicScope
for details.
The resources specified by the resource request parameters in
the preceding device authorization request. See "Resource Indicators
for OAuth 2.0" for details.
The scopes requested by the device authorization request for the user code.
Note that description and descriptions of each element (Scope
instance) in the scopes always null even if descriptions of
the scopes are registered.