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
I SOLEMNLY SWEAR THAT I HAVE SEARCHED DOCUMENTATION AND WAS NOT ABLE TO RESOLVE MY ISSUE
What protocol are you implementing?
FIDO2 Server
CTAP2.0
CTAP2.1
UAF 1.1
U2F 1.1
U2F 1.2
NOTE: UAF 1.0 certification have been officially sunset. U2F 1.2 only supported version of U2F.
What is your implementation class?
Security Key / FIDO2 / U2F authenticators
Server
UAF Client-ASM-Authenticator combo
UAF Client
UAF ASM-Authenticator
If you are platform authenticator vendor, please email [email protected]
What is the version of the tool are you using?
1.7.21.7
What is the OS and the version are you running?
Windows10
For desktop tools
OSX
Windows
Linux
For UAF mobile tools
iOS
Android
Issue description
When running the FIDO Alliance Conformance tool with an authenticator on which the max pin retry number is less than the max defined by the CTAP 2.1 specification (for example 3) the test in Authr-ClientPin1-GetRetries Test authenticatorClientPin(0x06), of version 0x01 support of getRetries(0x01) command fails
It is said that "
P-1 Send a valid CTAP2 authenticatorClientPin(0x01) message with getRetries(0x01) subCommand, wait for the response, and check that Authenticator returns CTAP1_ERR_SUCCESS(0x00) error code, and:
(a) check that authenticatorClientPin_Response contains "retries" field
(b) authenticatorClientPin_Response.retries is of type NUMBER
(c) authenticatorClientPin_Response.retries is extractly 8‣
"
(c) checks that the number of retries is 8 and this number is hard-coded in the test whereas CTAP2.1 specification says
Authenticators MUST allow no more than 8 retries but MAY set a lower maximum.
The text was updated successfully, but these errors were encountered:
iirachek
added
DONE
Has been implemented as part of one of the published releases
and removed
Awaiting Release
Is ready and is awaiting merge for the next release
labels
Nov 12, 2024
By submitting this issue you are acknowledging that any information regarding this issue will be publicly available.
If you have privacy concerns, please email [email protected]
FIRST PRE CHECK
What protocol are you implementing?
NOTE: UAF 1.0 certification have been officially sunset. U2F 1.2 only supported version of U2F.
What is your implementation class?
If you are platform authenticator vendor, please email [email protected]
What is the version of the tool are you using?
1.7.21.7
What is the OS and the version are you running?
Windows10
For desktop tools
For UAF mobile tools
Issue description
When running the FIDO Alliance Conformance tool with an authenticator on which the max pin retry number is less than the max defined by the CTAP 2.1 specification (for example 3) the test in Authr-ClientPin1-GetRetries Test authenticatorClientPin(0x06), of version 0x01 support of getRetries(0x01) command fails
It is said that "
P-1 Send a valid CTAP2 authenticatorClientPin(0x01) message with getRetries(0x01) subCommand, wait for the response, and check that Authenticator returns CTAP1_ERR_SUCCESS(0x00) error code, and:
(a) check that authenticatorClientPin_Response contains "retries" field
(b) authenticatorClientPin_Response.retries is of type NUMBER
(c) authenticatorClientPin_Response.retries is extractly 8‣
"
(c) checks that the number of retries is 8 and this number is hard-coded in the test whereas CTAP2.1 specification says
Authenticators MUST allow no more than 8 retries but MAY set a lower maximum.
The text was updated successfully, but these errors were encountered: