When the user attempts to log in to the Okta Dashboard, enter the credentials, and utilizes the Okta FastPass factor, the following error message appears: 
 
Something went wrong. Please try again.


 

• Okta Verify
• Windows
• Device Trust
• Okta Identity Engine

A skewed clock is one of the most common causes of this error. This will invalidate the token utilized by the Okta FastPass client and Okta. 

This can be confirmed by checking the Okta Verify Application Event Viewer Logs. Similar errors as below can be seen:

• Operation on enrollment pfdxxxxxxxxxx1t7 failed due to Okta server error: OktaWebException - Call to https://<domain>/idp/authenticators/pfdxxxxxxxxxx1t7 failed, HttpStatusCode=Unauthorized, Error='E0000011: Invalid token provided [oxxxxxxxxxxxT4g]',
• Failed to enroll device : Call to https://<domain>/idp/authenticators failed, HttpStatusCode=Unauthorized, Error='E0000011: Invalid token provided'"
• [FactorEnrollment][OktaApiWebRequest.HandleErrorResponse]: Received API error: E0000011: Invalid token provided
• AccountStateManager.InvokeTaskWithTracking: API error code InvalidToken detected
• [AccountEnrollment][OktaWebRequest.SendMessageAsync]: Call to https://<domain>/idp/authenticators failed with Unauthorized.

Please ensure the End user's clock configuration is set to Automatic Sync or Synced with an NTP Time Server.