-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use the WebAuthn API from MetaMask browser #4974
Comments
Anything I can do to move this forward? |
Hey @2pmflow can you try to reproduce the issue on v5.8 or v5.9? Thanks! |
@cortisiko I was able to reproduce the issue on v5.9 just now. |
@2pmflow that is a bummer. Okay, I will share this with the dev team. |
Needs product review @omnat . Please reach out to @sethkfman for product discussion. |
This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 7 days. Thank you for your contributions. |
Still interested in a solution |
Chiming in here, also interested in a solution. We closed an issue on one of our libraries based on this, but we can re-open as an indication of interest in Credential API support: arx-research/libhalo#178 |
Describe the bug
The MetaMask browser extension does not seem to support the WebAuthn. WebAuthn is currently supported on Chrome, Firefox, Edge, and Safari and enables authentication using public key cryptography.
Impact: this blocks certain authentication flows from taking place inside the MetaMask browser. For example, it's difficult to support an experience related to minting an NFT linked to a specific public key tied to a chip.
To Reproduce
Expected behavior
After clicking "Register", we expect to see a popup prompting the user to allow "webauthn.io" to use Face ID. You can repro this on a Chrome browser to see the expected behavior.
Smartphone (please complete the following information):
to be added after bug submission by internal support / PM
Severity
The text was updated successfully, but these errors were encountered: