Skip to main content

logintoken

The logintoken command authenticates a DisplayNet user via a login token, allowing sessions to persist without storing passwords locally.

Command TypeDisplayNet
Minimum Version3.x.x

Usage

logintoken <token>

Arguments

ArgumentRequiredDescription
tokenYesA valid login token, as returned in the LoginToken field of a successful login response.
Tokens expire

Login tokens have a configurable expiration period. An expired token returns "AuthState": "EXPIRED", and a token matching no user returns "AuthState": "RETRY". Both require re-authenticating with login.

Examples

Resume a session with a saved token
logintoken 9919abb5-24d0-4c56-bbf1-3df91998247c

Return value

logintoken 9919abb5-24d0-4c56-bbf1-3df91998247c
{
"status": "DN_AUTHENTICATION",
"request_id": null,
"result": null,
"error": null,
"auth_details": {
"IsAuthenticated": true,
"UserName": "DNAdmin",
"UserFullName": "DNAdmin",
"Role": "Admin",
"ClientAddress": "127.0.0.1:51684",
"AuthState": "COMPLETE",
"AuthenticationDateTime": "2026-07-31T22:55:00.9897486Z",
"ConnectionType": "Socket",
"LoginToken": "9919abb5-24d0-4c56-bbf1-3df91998247c"
}
}

REST API

No REST equivalent

This command acts on a single API session, so it has no REST operation. REST requests are independent of one another and have no session to act on. Over REST, obtain a token with POST /api/displaynet/login and send it on each request; see Authentication.

See also

  • login: authenticate with credentials (issues the token)
  • user: invalidate login tokens