Skip to main content

auth

The auth command authorizes a device against the server's device authentication key. Device authentication is a security feature, similar to claiming: once authentication is enabled, only authorized devices participate in the system.

Command TypeSDVoE
Minimum Version3.x.x
Requires the Admin role

Usage

auth <device> [<arguments>]

Arguments

ArgumentRequiredDescription
deviceYesDevice name, MAC address, or device ID. Names are substituted with the MAC address automatically.
argumentsNoAny additional arguments are passed through to the underlying SDVoE API command.
Changing the auth key

The server's device authentication key is the device_auth_key value, set via the config command (server scope; readable only as Admin). Key changes require a service restart. Apply them with server applypending before authorizing devices.

Examples

Authorize a device by name
auth room_projector

Return value

auth is processed asynchronously. The immediate reply is PROCESSING with a request_id. Read the outcome with request.

auth room_projector
{
"status": "PROCESSING",
"request_id": 42,
"result": null,
"error": null
}

Errors

ErrorCause
Server Claim/Auth Key change is pending...A claim/auth key change has not been applied yet. Run server applypending first
Invalid parametersNo device was given

REST API

Although auth originates in the SDVoE API, the REST example below uses a DisplayNet API operation. Use the endpoint shown here. DisplayNet uses it to maintain its own device records.

Endpoint typeDisplayNet API command
AddressPOST /api/displaynet/<operation>, or name the operation in the body of a POST /api/displaynet. See Sending commands.
RoleAdmin
OperationParameters
authdevice [args]*

A parameter in brackets is optional. A parameter marked * takes the remainder of the command line as one string. Pass the text exactly as you would type it on the TCI interface.

See also