Package com.nimbusds.oauth2.sdk.device

Class DeviceAuthorizationGrantError

java.lang.Object

com.nimbusds.oauth2.sdk.device.DeviceAuthorizationGrantError

public final class DeviceAuthorizationGrantError
extends Object

OAuth 2.0 Device Authorization Grant specific errors.

Related specifications:

• OAuth 2.0 Device Authorization Grant (RFC 8628)

Field Summary

Fields

Modifier and Type	Field	Description
static final ErrorObject	AUTHORIZATION_PENDING	The authorization request is still pending as the end user hasn't yet completed the user interaction steps (Section 3.3).
static final ErrorObject	EXPIRED_TOKEN	The "device_code" has expired and the device flow authorization session has concluded.
static final ErrorObject	SLOW_DOWN	A variant of "authorization_pending", the authorization request is still pending and polling should continue, but the interval MUST be increased by 5 seconds for this and all subsequent requests.

Method Summary

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Details

AUTHORIZATION_PENDING

public static final ErrorObject AUTHORIZATION_PENDING

The authorization request is still pending as the end user hasn't yet completed the user interaction steps (Section 3.3). The client SHOULD repeat the Access Token Request to the token endpoint (a process known as polling). Before each new request the client MUST wait at least the number of seconds specified by the "interval" parameter of the Device Authorization Response (see Section 3.2), or 5 seconds if none was provided, and respect any increase in the polling interval required by the "slow_down" error.

SLOW_DOWN

public static final ErrorObject SLOW_DOWN

A variant of "authorization_pending", the authorization request is still pending and polling should continue, but the interval MUST be increased by 5 seconds for this and all subsequent requests.

EXPIRED_TOKEN

public static final ErrorObject EXPIRED_TOKEN

The "device_code" has expired and the device flow authorization session has concluded. The client MAY commence a new Device Authorization Request but SHOULD wait for user interaction before restarting to avoid unnecessary polling.