Set userVerification to preferred in registration options #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
userVerification
is set to"preferred"
so that user verification is only attempted when possible (i.e. biometric authentication methods like TouchID are presented when available, but it is not required for successful authentication).userVerification
is not specified. Because of this,userVerification
is required as this is the default in SimpleWebAuthn'sverifyRegistrationResponse
. This presents an issue during the registration flow when using iCloud Keychain or Chrome's built in passkey manager when no user verification method is available (e.g. when a MacBook is in clamshell mode and therefore TouchID is not present/available). In this case, the follow error is returned fromauthenticator.authenticate()
:User verification required, but user could not be verified
.userVerification: "preferred"
on the registration flow as well so that the user verification behaviour is consistent in both flows. This follows the guidance fromweb.dev
on how to specify theuserVerification
parameter.