Passkey Popup

176 views
Skip to first unread message

HYUN TAEK

unread,
Mar 13, 2025, 4:44:13 AMMar 13
to FIDO Dev (fido-dev)
Hello : )

I was a Windows 10 user and recently upgraded to Windows 11 24H2.

In Windows 10, the UI for Windows Hello and passkeys using mobile was provided within the browser. However, in Windows 11, I noticed that the UI is now provided inside the Windows Hello pop-up window.

In Windows 10)
UI_windows10.JPG

In Windows 11)
UI_windows11.JPG


<Questions>

1. Are there any documents or links that explain this UI change?
2. Is there a way to change this behavior in Windows 11 so that the UI is provided in the browser pop-up window, similar to Windows 10, instead of the Windows Hello pop-up window?

Pro Coder 101

unread,
Mar 13, 2025, 6:46:58 AMMar 13
to HYUN TAEK, FIDO Dev (fido-dev)

Hey,
Windows Hello supports FIDO from Win 10 version 1903 (May 2019 update). Could you confirm whether the windows 10 version you were using were higher or lower than this?

Before that FIDO was entirely handled by the browser. Now Windows Hello added a file called webauthn.dll that supports FIDO natively. There may be browser implementations that still supports FIDO through browser. (You may look into downgrading your browser if absolutely necessary, though it is not recommended.)


--
You received this message because you are subscribed to the Google Groups "FIDO Dev (fido-dev)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fido-dev+u...@fidoalliance.org.
To view this discussion visit https://groups.google.com/a/fidoalliance.org/d/msgid/fido-dev/69b61fca-912f-40ca-a535-2f151cfdf6a4n%40fidoalliance.org.

Tim Cappalli

unread,
Mar 13, 2025, 9:09:52 AMMar 13
to HYUN TAEK, FIDO Dev (fido-dev)
Chrome and Edge provide authenticator selection on Windows 10 as the OS does not natively support Cross-Device Authentication, whereas Windows 11 does. 

This is not user configurable. 

If the user uses Google Password Manager, Chrome may still show a limited dialog on Windows 11.

--
Reply all
Reply to author
Forward
0 new messages