# UserVerification setting in Auth0 Passkey

**URL:** <https://community.auth0.com/t/userverification-setting-in-auth0-passkey/197276>\
**Category:** Product Feedback\
**Created:** [February 13, 2026, 4:22pm UTC](https://community.auth0.com/t/userverification-setting-in-auth0-passkey/197276 "2026-02-13T16:22:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jboomhower](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jboomhower/32/73016_2.png) [@jboomhower](https://community.auth0.com/u/jboomhower)\
**Post date:** [February 13, 2026, 4:22pm UTC](https://community.auth0.com/t/userverification-setting-in-auth0-passkey/197276/1 "2026-02-13T16:22:23Z")

</div>

**Feature:** Allowing Setting UserVerification Value in Passkey

**Description:** Currently, for the Passkey MFA option under Auth0, the UserVerification value is hardcoded to Preferred. There is currently not any way to update this to Required. We would like this to be updated to allow for Admin access to the value.

**Use-case:** Our implementation of Auth0 supports the data entry of medical information that includes PII. Due to the overhead of security policies and our need to adhere to global governance of all kinds, the inability to set UserVerification to Required means that Passkey as a solution does not meet our security requirements. Specifically, the storage of a passkey within Google Password Manager in Chrome on a Windows device translates the Preferred UserVerification value by allowing any user who is in that browser on that machine to single click approval for the passkey without secondary require authentication. To meet the security requirements of our implementation, specifically to meet governance adherence matching GDPR, we need to block this authentication path by setting UserVerification to Required.

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [March 4, 2026, 6:20pm UTC](https://community.auth0.com/t/userverification-setting-in-auth0-passkey/197276/3 "2026-03-04T18:20:05Z")

</div>

Hi @jboomhower

Thank you for submitting the feature card!

Currently, there is a backlog item addressing this feature, however, there is no ETA at this time for when it will become available.

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![dallas.norton](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dallas.norton/32/81654_2.png) [@dallas.norton](https://community.auth0.com/u/dallas.norton)\
**Post date:** [November 10, 2026, 6:53am UTC](https://community.auth0.com/t/userverification-setting-in-auth0-passkey/197276/4 "2026-11-10T06:53:36Z")

</div>

Hi! Is there any update on this backlog item, or a rough timeline?

We have the same need. Our compliance requirements only let a passkey sign-in count as MFA when the user was verified with a biometric or PIN. Today, database-connection passkeys in Universal Login always use `userVerification: "preferred"`. In our testing, a Mac with Touch ID unavailable created a passkey and signed in with no biometric or password prompt, and the UV flag was false.

Either of these would solve it for us:

1. A setting to require user verification (`userVerification: "required"`) for passkey enrollment and sign-in, with Auth0 rejecting sign-ins where the UV flag is false.
2. Showing the UV flag in the post-login Action event (for example in `event.authentication.methods`), so an Action can skip MFA only when the user was verified.

Thanks!
