You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
E.g. using the virtual authenticators tab extension in chrome dev-tools it seems to be possible to set up a credential and login with that credential, using a virtual authenticator which does not support user verification.
If requiring user verification is not working in the backend, then we can’t rely on Webauthn to provide both factors for 2FA.
Related, the javascript doesn’t seem to be passing the requirement for userverification to the webauthn JS API, which may mean a confusing user experience where a key (without user verification) seems to be acceptable on the FE and then is rejected on the BE.
The text was updated successfully, but these errors were encountered:
- coverage all compliance tests
- metadata verification
- TPM attestation support
- Apple attestation support
- UserVerificationRequirement support
closesgravitee-io/issues#4496
- coverage all compliance tests
- metadata verification
- TPM attestation support
- Apple attestation support
- UserVerificationRequirement support
closesgravitee-io/issues#4496
E.g. using the virtual authenticators tab extension in chrome dev-tools it seems to be possible to set up a credential and login with that credential, using a virtual authenticator which does not support user verification.
If requiring user verification is not working in the backend, then we can’t rely on Webauthn to provide both factors for 2FA.
Related, the javascript doesn’t seem to be passing the requirement for userverification to the webauthn JS API, which may mean a confusing user experience where a key (without user verification) seems to be acceptable on the FE and then is rejected on the BE.
The text was updated successfully, but these errors were encountered: