Authentication fails when using discoverable credentials created on external NFC authenticators that do not support ClientPIN.
8 views
Skip to first unread message
jy
3:26 PM (2 hours ago) 3:26 PM
to FIDO Dev (fido-dev)
Steps to Reproduce
- Use an external NFC authenticator that does not support ClientPIN.
- Visit Webauthn.io on an Android device.
- Register a discoverable credential using the NFC authenticator.
- Attempt to authenticate with the newly created credential.
- Android displays: "Something went wrong" and hangs there.
Expected Behavior
Authentication should succeed, similar to behavior observed on iOS.
If ClientPIN is not supported on the authenticator, the NFC interaction should be sufficient to establish User Presence (UP), allowing assertion or registration to proceed.
- Use an external NFC authenticator that does not support ClientPIN.
- Visit Webauthn.io on an Android device.
- Register a discoverable credential using the NFC authenticator.
- Attempt to authenticate with the newly created credential.
- Android displays: "Something went wrong" and hangs there.
Expected Behavior
Authentication should succeed, similar to behavior observed on iOS.
If ClientPIN is not supported on the authenticator, the NFC interaction should be sufficient to establish User Presence (UP), allowing assertion or registration to proceed.
Reply all
Reply to author
Forward
0 new messages