Closed hase77 closed 2 years ago
This is a problem of Android. Android requires that it is told by the server which key ids are allowed to authenticate. If an empty array comes from the server, the android chrome browser simply stops and gives an error.
But the problem is that with Fido we can't just send all the registered ids to the client. With 2FA WebAuthn it works, because here a username and password is needed. The credentials are then used to see which key IDs are stored that are allowed to authenticate.
Since Fido does not require a username or password, we would have to send all key ids from the database back to the client. With a larger number of users this could lead to problems.
As soon as Android supports discoverable Credentials this bug will be fixed.
https://developers.yubico.com/WebAuthn/WebAuthn_Browser_Support/
Contribution guidelines
I've found a bug and checked that ...
Description
Try to authenticate with an Fido2 security key (Nitrokey 3A) on Android with mobile Chrome does not work and result in following error message:
Validation failed: Use of an empty àllowCredetianls list is not supported on this device.
Authentication on Windows with Firefox or Chrome works fine. Google Pixel 4a 5G with Android 13 and mobile Chrome 106.
Logs
Steps to reproduce
System information
docker version
)docker-compose version
)git describe --tags `git rev-list --tags --max-count=1`
)Output of
git diff origin/master
, any other changes to the code? If so, please post them:All third-party firewalls and custom iptables rules are unsupported. Please check the Docker docs about how to use Docker with your own ruleset. Nevertheless, iptabels output can help us to help you: iptables -L -vn:
ip6tables -L -vn:
iptables -L -vn -t nat:
ip6tables -L -vn -t nat:
DNS problems? Please run
docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254
(set the IP accordingly, if you changed the internal mailcow network) and post the output: