This article reviews a FastPass authentication failure log message that may be identified in the Windows Event Viewer log for Okta:
[CustomUriRequest][DeviceProbingBindingRequestTask.SetFailure]: Failed to send verify message: Call to https://<domain>/idp/authenticators/<AuthenticatorEnrollmentID>/transactions/<TransactionID>/verify failed, HttpStatusCode=BadRequest, Error=': '.
Full log message:
Log Name: Okta
Source: Okta Verify
Date: 10/25/2024 0:01:01 AM
Event ID: 8130
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: <ComputerName>
Description:
[CustomUriRequest][DeviceProbingBindingRequestTask.SetFailure]: Failed to send verify message: Call to https://<domain>/idp/authenticators/<AuthenticatorEnrollmentID>/transactions/<TransactionID>/verify failed, HttpStatusCode=BadRequest, Error=': '.
This log may accompany a FastPass authentication failure or authentication looping behavior. While troubleshooting this behavior with a Browser Capture, this event will usually be observed as an HTTP 502 Bad Gateway error response to the FastPass authentication probing challenge:
- Okta Identity Engine (OIE)
- Okta Verify FastPass
- Error Logs
This behavior is known to be caused by Time Skew (Wrong date/Time setting) on the local machine.
If the Time Skew (time, time zone, and date) is correct, the customer's firewall may be causing this.
To resolve this issue, correct the Date and Time configured on the local machine. Consider also configuring the timezone to set automatically so that regular synchronization with an NTP server occurs and prevents time skew from reoccurring.
If the Time Skew (time, time zone and date) are correct, then this can be also caused the customer's firewall.
