Skip to content
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

Platofrm authenticators (TouchID/FaceID and Windows Hello) not suported #5790

Closed
tmccal2 opened this issue Jan 6, 2022 · 2 comments
Closed

Comments

@tmccal2
Copy link

tmccal2 commented Jan 6, 2022

Steps to reproduce the issue (please be as specific as possible)

Log in to login.gov, then select "Add Security Key" beneath "Your Authenticators".

Expected behavior

[macOS/iOS] The authentication prompt opens, asking to use FaceID/TouchID
[Windows 10/11] The authentication prompt opens, asking to use Windows Hello for authentication.

In both of these prompts, there should be a link to instead authenticate with a security key.

Actual behavior

On both ends, it only asks for a security key.

I think this is occurring because the webauthn javascript code explicitly sets the authenticatorSelection.authenticatorAttachment option to 'cross-platform' when registering a new credential. Not setting this property can allow for both cross-platform authenticators (such as a Yubikey) and platform authenticators (such as your mobile device).

If we remove the following line and keep user_verification to 'discouraged', it should still keep users from being required to enter a PIN number to authenticate, but should also allow use of TouchID/FaceID and Windows Hello.

authenticatorSelection: {
// Prevents user from needing to use PIN with Security Key
userVerification: 'discouraged',
authenticatorAttachment: platformAuthenticator ? 'platform' : 'cross-platform',
},

Otherwise, what is the rationale forbidding use of FaceID/TouchID and Windows Hello?

@mitchellhenke
Copy link
Contributor

Thanks for opening this issue!

We have implemented support for Platform Authenticators (#5632), but have not yet enabled it just yet (my hope is we do that soon 🙂).

@mitchellhenke
Copy link
Contributor

This feature was released today! 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants