3.2.5.3.1 POST

This operation is transported by an HTTP POST.

The operation can be invoked through the following URI:

 /devicecode?client-request-id={ClientRequestId}

The format of the device authorization token request is specified in [RFC8628] section 3.1 (Device Authorization Request). The OAuth 2.0 client can choose to send the client-request-id query parameter.

client-request-id: OPTIONAL. The client can choose to specify this optional query parameter to specify a request ID which is used when logging errors or failures that occur while processing the request.

The request message for this method can contain the following optional HTTP headers. The header syntax is defined in section 2.2.1.

Request header

Usage

Value

client-request-id

This optional header is used to specify a request identifier which is used when logging errors or failures that occur while processing the request.

A request identifier, which MUST be a GUID.

The response message for this method does not contain any custom HTTP headers.

The response message for this method can result in the status codes defined in [RFC6749] section 5.2 (Error Response). Additionally, if the AD FS server encountered an error while processing the client's access token request, it can return the server_error error code defined in this document.