fdeaz
Failed Device Confirmation - Request Failure
Client name associated with the client_id, when available. May be empty string.
Description of the event. This can also contain a description of the issue for failure logs.
Log details
The name of the environment where the event occurred
"prod-eu-1"
"prod-us-1"
The hostname associated with the request. For forwarded requests, this should resolve to the original hostname. For failure logs, this may include invalid hostnames.
The IP address associated with the request. For an auth related log this should be the end user IP. For a machine-to-machine auth flow this should be the IP of the computer doing the authentication. For management logs like sapi and mgmt_api_read this should be the IP of the admin using the manage dashboard.
Log id
Tenant name
Failed Device Confirmation - Request Failure
"fdeaz"Event schema meta
Client related to the API call. Clients are also called applications. The underlying application may not be owned by your tenant and may not be accessible. For failure logs, this may be a valid ID, an invalid one, or any ID.
Name of the connection, when available. The connection here matches the connection_id field.
ID of the connection on which the auth flow is happening or connection of the user doing the action, when applicable. For failure logs this field may contain an invalid ID.
The date when the event occurred in ISO 8601 format
"2024-01-15T10:30:00.000Z"
Whether the request originated from a mobile device. Only present when user_agent is available.
The user_agent behind this log, when available
"Chrome 120.0.0 / Mac OS X 10.15.7"