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

Error: Unexpected authenticator counter: 0 (should be > 0) #27

Closed
jmatsushita opened this issue Jul 21, 2023 · 2 comments
Closed

Error: Unexpected authenticator counter: 0 (should be > 0) #27

jmatsushita opened this issue Jul 21, 2023 · 2 comments

Comments

@jmatsushita
Copy link

When using the playground both in Chrome on Desktop and Mobile (iOS):

  • I can Register Device succesfully with the default settings
  • When I press Login the client side details are filled up
  • But a toaster shows up with this error Error: Unexpected authenticator counter: 0 (should be > 0) and the second server side area shows:
Resulting into:
...
@dagnelies
Copy link
Collaborator

According to the WebAuthn specification, this counter should increase each time authentication is triggered with the key... In theory. In practice, Windows and Android do respect that, but Apple sets it to zero... And I don't actually know if they increase it at all since I don't have such a device to test.

I recommend to use counter:-1 to verify the first attestation instead of 0. And I would be curious if they properly increase this counter afterwards.

@dagnelies
Copy link
Collaborator

I will also edit the playground accordingly soon

dagnelies added a commit that referenced this issue Jul 23, 2023
Follow up of #27
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