After it receives the authentication request, your appliance authenticates the user account and responds with either an authentication confirmation code, along with an API-Token used to maintain the authenticated session, or an authentication invalid code.
HTTP/1.1 [Response Code] [Response Message]
Date: [Date]
X-FeApi-Token: [API-Token]
X-FeClient-Token: [Client-Token]
Response fields
Response Code—A standard HTML response code.
200—Authentication Success
401—Authentication Refused
503—Web Services API server disabled
Response Message—A standard HTML response message.
OK—Authentication Success
Unauthorized—Authentication Refused
Not available—Web Services API server disabled
Date—Standard HTML date format
API-Token—This token authenticates the session. By default, the session times out after 15 minutes of inactivity.
Client-Token—(Optional) This client token is provided by Trellix. For more information about the client token, contact your sales representative.
Example
The following is an example of a valid response received from an appliance.
HTTP/1.1 [Response Code] [Response Message] Date: Fri, 20 Oct 2017 08:00:00 X-FeApi-Token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx X-FeClient-Token: BigDataInc