<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language

Okta FIDO2 Passkey Enrollment Failures and Abandoned System Log Events

Okta Classic Engine
Okta Identity Engine
Multi-Factor Authentication

Overview

End-users experience a deadlock where a primary security key or biometric authenticator stops working after attempting to set up a second Multi-Factor Authentication (MFA) device. This occurs due to local device overwrites or hardware protection policy enforcement, and administrators observe an abandoned MFA event in the Okta System Log. Administrators resolve this by resetting the authenticator, customizing the end-user interface, or reviewing security policies.

 

Authentication of user via MFA ABANDONED

 

WebAuthn authenticator hardware protected check failed, mdsValidation=FAIL due to non-success attestation validation during enrollment.

 

Applies To

  • Okta Identity Engine (OIE)
  • Okta Classic Engine
  • FIDO2 (WebAuthn) Authenticators
  • Passkeys
  • Windows Hello
  • Apple iCloud Keychain
  • Google Password Manager
  • Microsoft Password Manager
  • Physical Security Keys

Cause

This behavior results from standard third-party FIDO2 hardware specifications combined with Okta enforcing Zero Trust security policies.

 

According to FIDO2 industry specifications, authenticators store one credential per relying party for a specific end-user. When an end-user attempts a duplicate setup on the exact same device, the local operating system or password manager silently overwrites the original private key to accommodate the new one. If the end-user views duplicate entries in the Okta End-User Dashboard and manually deletes the new entry, a dead credential remains on the profile. When Okta issues an authentication challenge for this dead credential, the local machine cannot find the private key and forcefully terminates the connection. Okta logs this as an abandoned event because the browser drops the WebAuthn ceremony before Okta completes the check.

 

Additionally, if administrators enable a hardware-protected constraint in the App Sign-On policies, or if they activate the block synced passkeys feature, Okta actively rejects enrollments from software-synced password managers. Okta evaluates the device attestation against the global FIDO Alliance Metadata Service (MDS). Because synced passkeys are software-based and exportable, they fail the MDS attestation check. The browser subsequently aborts the enrollment, resulting in the abandoned log.

Solution

What steps reset the authenticator?

Reset the broken FIDO2/WebAuthn factor to clear the dead credential and provide a clean slate for re-enrollment.

  1. Navigate to the Okta Admin Console.
  2. Locate the impacted profile.
  3. Execute the Reset Authenticators action for the broken FIDO2/WebAuthn factor.

 

Interface Customization Prevents Credential Overwrites

Configure a custom user interface warning to prevent end-users from overwriting credentials when enrolling physical USB security keys.

  1. Navigate to the Authenticator settings for Passkeys / FIDO2 (WebAuthn) in the Okta Admin Console.
  2. Enable a Custom name and description.
  3. Add a warning text to intercept behavior before the browser modal renders.

 

What steps review security policies for software-synced passkeys?

Review active authentication policies to permit the use of software-synced passkeys rather than strictly enforcing physical hardware keys.

  1. Review the active Authentication Policies and remove the hardware protection constraint.
  2. Verify in Settings > Features that the block synced passkeys for FIDO2 (WebAuthn) Authenticators feature is disabled.
Loading
Okta FIDO2 Passkey Enrollment Failures and Abandoned System Log Events | Okta Support