I receive a "Could not verify your identity because the system clock is too far ahead or behind" error

This article provides an overview of the "system clock is too far ahead or behind" error message and how to recover and authenticate again.

What's the issue?

When attempting to authenticate, I am presented with the following error:

"Could not verify your identity because the system clock is too far ahead or behind and failed the verification window."

This error occurs when a user's system clock is manually set and drifts in the future by more than 15 minutes or in the past by more than 70 minutes and cannot be validated within the verification window. For example, if the system clock is ahead by 20 minutes and the authenticator's verification window is 10 minutes, although only 2 minutes have passed in actuality, the system clock shows 20 minutes have passed.  

Error message example: 

What’s the solution?

This error can be resolved by setting the time and date correctly on that specific device. We recommend having the operating system set the time and date automatically.

Still need help? Contact support at support@beyondidentity.com