<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

Understanding Why Windows Devices Cannot Satisfy the "Require Biometric User Verification" Okta Authentication Policy Option

Okta Identity Engine
Okta Verify

Overview

Windows devices fail to satisfy the biometric user verification requirement in Okta Authentication Policies because Microsoft Windows Hello requires a Personal Identification Number (PIN) fallback, preventing the creation of a biometric-only key. Configure separate Authentication Policy rules for Windows and non-Windows devices to resolve this issue. When an App Sign-In Policy rule requires biometric user verification, Okta blocks Windows users attempting to sign in with Okta FastPass and Windows Hello. Okta displays a remediation screen, even when the user scans their face or fingerprint.

Enable Windows Hello or passcode confirmation in Okta Verify. To meet your organization's requirements, try the following, then return here and sign in again:

Make sure Okta Verify is up-to-date

In Okta Verify, enable Windows Hello or passcode confirmation for your account

The user.authentication.auth_via_mfa event records an outcome of SUCCESS with keyTypeUsedForAuthentication: USER_VERIFYING_BIO_OR_PIN and MethodUsedVerifiedProperties includes USER_VERIFYING, not USER_VERIFYING_BIO_ONLY. However, Okta stops the user at the remediation screen and denies access to the application.

Applies To

  • Okta Identity Engine (OIE)
  • Okta Verify for Windows (Okta FastPass)
  • Windows Hello (PIN, Facial Recognition, Fingerprint)
  • Application Sign-In Policy (Authentication Policy) with Require biometric user verification

Cause

Okta only supports the Require biometric user verification option on Android, iOS, and macOS. Okta does not support it on Windows devices. Microsoft Windows Hello always requires configuring a Windows Hello PIN as a fallback, even when the user enables Facial Recognition or Fingerprint. Windows Hello binds Facial Recognition, Fingerprint, and PIN to the same underlying cryptographic key container (Microsoft Passport Key Storage Provider) and does not disclose to applications which method unlocked the key during a sign-in challenge. Because Windows cannot create a biometric-only private key that excludes PIN fallback, Windows Okta Verify registers the Windows Hello key as USER_VERIFYING_BIO_OR_PIN.

 

When a policy rule requires biometric user verification, Okta requires a USER_VERIFYING_BIO_ONLY key. Because a Windows device only possesses a USER_VERIFYING_BIO_OR_PIN key, it cannot satisfy the biometric-only requirement, and Okta displays the standard User Verification remediation prompt.

 

In Okta Identity Engine, factor verification and policy evaluation are separate steps. The user.authentication.auth_via_mfa event indicates only that the device's USER_VERIFYING_BIO_OR_PIN key validly signed the cryptographic FastPass challenge (SIGNED_NONCE). Because USER_VERIFYING_BIO_OR_PIN does not satisfy the rule's USER_VERIFYING_BIO_ONLY requirement, the sign-in flow halts at the remediation screen and never issues an application sign-on ALLOW event (policy.evaluate_sign_on / user.authentication.sso). Furthermore, because the Windows Operating System (OS) does not report to Okta whether PIN, Fingerprint, or Facial Recognition unlocked the Windows Hello key, the System Log only records the key type (USER_VERIFYING_BIO_OR_PIN), not the physical gesture used.

Solution

How are separate Authentication Policy rules configured by platform?

Configure separate Authentication Policy rules for non-Windows devices and Windows devices by creating a rule for macOS, iOS, and Android that requires biometric user verification, and a separate rule for Windows that requires device passcode or biometric user verification.

  1. Create a rule for non-Windows devices and set the Platform condition to macOS, iOS, and Android, and set the User interaction to Require biometric user verification.
  2. Create a rule for Windows devices and set the Platform condition to Windows, and set the User interaction to Require device passcode or biometric user verification.

 

Loading
Understanding Why Windows Devices Cannot Satisfy the "Require Biometric User Verification" Okta Authentication Policy Option | Okta Support