-
**Describe the bug**
Whenever I try to use the new FIDO functionality via USB on v0.2.25.223616 or [2a19ef4](https://github.com/microg/GmsCore/commit/2a19ef45de5ad43bb3101f72aff477a2fc491e68), the tr…
-
**systemd version the issue has been seen with**
> v248
**Used distribution**
> Arch Linux
**Linux kernel version used** (`uname -a`)
> `Linux unicorn 5.11.11-arch1-1 #1 SMP PREEMPT Tue, 3…
-
This issue is to track progress on the addition of a network transport, which is mostly happening in FIDO world. Here is a summary of progress so far:
* @arnar, @nicksteele and I discussed the issu…
-
Hi,
Amazing project, congratulations. I was using just a simple Wroom 32 development board to test the FIDO2 authentication protocol with BLE. Using chrome on windows 10 gives the following error i…
-
Dear Strongkey Support,
We are successfully able to deploy Strongkey FIDO Open source server. Also we deployed sample java web application (https://github.com/strong
key/fido2/tree/master/sampleap…
-
Google Chrome is starting to deprecate the U2F API and is asking developers to use WebAuthn instead.
U2F devices are still supported through WebAuthn and existing U2F device credentials can be chal…
-
Hi,
I'm using Keycloak 15 with keycloak-provider 1.0.0 (also have this issue with 0.6.1).
When I configure two webauthn tokens for a user and then try to login on keycloak as that user, the dial…
-
In creation there is no way to specify to the user agent which transports we allow, since we only have:
https://www.w3.org/TR/webauthn-3/#dictdef-authenticatorselectioncriteria
https://www.w3.org/…
-
**Describe the bug**
Using "Authenticate using a Device" I am still asked for a username and and asked to use my device to authenticate. At the next step I'm choosing WebAuthn as SFA method.
Aft…
-
### Expected behavior
After WebAuthN failed register/login, the device should still work as usual, like before the operation
### Actual behavior
After WebAuthN failed register/login, _canceled by…