Multifactor authentication using windows security key #3947
Unanswered
sachin-jose
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am working on a webview2 supported MFA application prototype to enhance FIDO2 USB/biometric device authentication. It was developed for Windows 1809 build(LTSC 2019) OS. Windows native security key option is not available in this OS version, instead, a browser embedded popup is available to detect the device and achieve MFA.
Fig1: Browser embeded security popup
Fig2: Windows native security key dialog
In the latest Windows OS, authentication through the device is achieved through the native windows security key, not with the browser embedded popup. When I investigated, I came to know that after a particular windows version the device authentication support is done through windows native security key. The browsers including webview2 also switched to this option.
My requirement is to use the browser embedded popup for device detection, due to the reason that the native windows security dialogue does not appear in a custom desktop(programmatically created desktop).
I used the command-line option(--disable-features="WebAuthenticationUseNativeWinApi"), in the webview2 test application and edge browser, to show browser embedded popup instead of windows native security dialog. The popup appears, but the device is not detected when I use this option in the latest OS. But when I tried with chrome browser, the device detected with security popup.
I am trying to find the reason why the device is not detected while using an edge browser/webView2 app with embedded security popup in the latest OS.
Any help will be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions