Passwordless login using a security key doesn't work
Describe the bug After having setup passwordless login, which I can confirm to be working by using Face ID on my phone, on either iOS or Chrome (Win11), won't allow login with my YubiKey ("This security key doesn't look familiar, please try a different one" error on the Windows security popup)
To Reproduce Steps to reproduce the behavior:
- Set up a Webauthn security key on your account
- Set up a flow as described in the documentation, and apply it to the main login flow
- Try to log in using the security key added above
- See error
Expected behavior The security key login should work normally, as does the Face ID login I have set up.
Screenshots
Logs No relevant logs have been found - Only health checks.
Version and Deployment (please complete the following information):
- authentik version: 2023.10.2
- Deployment: Docker compose, under Traefik
Additional context If any additional information/screenshots is required, please let me know.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
no stale
This bug is affecting me as well.
I think I've figured out a workaround, or maybe this issue is just a documentation problem. I had to bind an identification stage to my passwordless login flow, so the user has a chance to enter their username. Then the WebAuthn authentication can proceed as normal. However, this does lead to a pretty confusing flow of:
- Being prompted for a username, but clicking the passwordless option instead
- Being prompted for a username again, entering it here
- Authenticaiton via WebAuthN
- Successful login
Going directly to the passwordless authentication flow URL avoids step 1.
In short, I think it works, but I think I'll have to do some learning on how to make it work well in Authentik. Either way, I'm now able to log in using my Yubikey.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
No stale
I also had this problem and implemented the workaround by @jroose.
After some more digging, I changed my WebAuthn setup stage settings: "Resident key requirement" and "User verification" was "Preferred", I changed them to "Required". Then I unregistered the WebAuthn device from my account and re-added it.
Now the passwordless flow works without the additional identification stage.
We'll be adding some UI improvements and docs improvements to better clarify which settings in the stages should be set to what values for different use-cases/platforms/authenticators