Authentication Mechanisms#

For the supported Agent routes, including activity checks, Discovery Agent sends its GUID in the Authorization: Basic <base64(GUID)> header. The server associates the Agent or project GUID with an Account. This is a separate mechanism, unrelated to API tokens created by a User in the API section.

A User signs in to the Discovery Server web interface with a username and password. The browser then uses a session cookie. When the User is inactive, the server settings limit the session lifetime. It is important to use HTTPS when transmitting credentials and GUIDs.