Q100550: Why Flix's security protocol may forcibly log users out
This article will explain why it is important that your machine’s date, time and timezone are set correctly to be able to log in to the Flix Client.
All communication between the Flix Client and the Flix Server goes through a security mechanism which checks for the validity of the requests. The correct date/time of the machines Flix operates on is an important component within this security mechanism.
When a user is logged into the Client, the Server takes the Client’s machine’s date, time, and timezone, converts everything to the Coordinated Universal Time (UTC) and compares the time to its own (also converted to UTC).
If there is a difference of more than 15 minutes between the two UTC time results, the Server’s security mechanism will prevent the Client to access secure Flix data, causing an authentication error. This will not allow the user to log into the Client if they were trying to log in, or forcibly log them out if already logged in; in both cases, the following message will be displayed in the Client:
The Server logs will also show an error stating
invalid or no date header as well as
invalid authentication header and
We recommend using the Network Time Protocol (NTP) for accurate time setting on all machines running Flix, as it allows the synchronisation of computers to within a few milliseconds of the Coordinated Universal Time (UTC). This means that the Flix Client and Server machines will be in sync when communicating, fulfilling the Flix security mechanism used for data validation.
If you are using NTP on all machines running Flix Clients and Servers, but continue to experience issues, then please open a Support ticket and let us know the issue you are encountering and the troubleshooting steps you have taken so far.
For more information on how to do this, please see the following article: Q1000064: How to raise a support ticket.
We're sorry to hear thatPlease tell us why