import { DeviceAuthorizationResponse } from "https://deno.land/x/authlete_deno@v1.2.10/mod.ts";
Enums
The next action that the service implementation should take. |
import { DeviceAuthorizationResponse } from "https://deno.land/x/authlete_deno@v1.2.10/mod.ts";
Response from Authlete /device/authorization
API.
Properties
The list of ACR values requested by the device authorization request.
Basically, this property has the value of the acr_values
request
parameter in the device authorization request. However, because
unsupported ACR values are dropped on Authlete side, if the acr_values
request parameter contains unrecognized ACR values, the list this
property has becomes different from the value of the acr_values
request parameter.
If the request does not include the acr_values
request parameter,
the value of the default_acr_values
client metadata is used.
The next action that the implementation of the device authorization endpoint should take.
The authorization details. This represents the value of the
authorization_details
request parameter which is defined in
"OAuth 2.0 Rich Authorization Requests".
Arbitrary attributes associated with the client.
The client authentication method that should be performed at the device authorization endpoint.
The client ID of the client application that has made the device authorization request.
The client ID alias of the client application that has made the device authorization request.
The client ID alias of the client application that has made the device authorization request.
The name of the client application which has made the device authorization request.
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 always 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 device verification code. This corresponds to the device_code
property in the response to the client.
The dynamic scopes which the client application requested by the
scope
request parameter. See the description of DynamicScope
for details.
The duration of the issued device verification code and end-user
verification code in seconds. This corresponds to the expires_in
property in the response to the client.
The minimum amount of time in seconds that the client must wait
for between polling requests to the token endpoint. This corresponds
to the interval
property in the response to the client.
The resources specified by the resource
request parameters.
See "Resource Indicators for OAuth 2.0" for details.
The content that can be used to generate a response to the client application.
The scopes requested by the device authorization request.
Basically, this property has the value of the scope
request
parameter in the device authorization request. However, because
unregistered scopes are dropped on Authlete side, if the scope
request parameter contains unknown scopes, the list this property
has becomes different from the value of the scope
request parameter.
Note that description
property and descriptions
property of
each element (Scope
instance) in the array returned from this
method always return null
even if descriptions of the scopes
are registered.
Arbitrary attributes associated with the service.
The end-user verification code. This corresponds to the user_code
property in the response to the client.
The end-user verification URI. This corresponds to the verification_uri
property in the response to the client.
The end-user verification URI that includes the end-user verification
code. This corresponds to the verification_uri_complete
property
in the response to the client.