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

FIDO registration fails for Authentrend and TrustKey Security Keys #228

Closed
swoozey opened this issue May 4, 2021 · 0 comments · Fixed by #229
Closed

FIDO registration fails for Authentrend and TrustKey Security Keys #228

swoozey opened this issue May 4, 2021 · 0 comments · Fixed by #229

Comments

@swoozey
Copy link
Contributor

swoozey commented May 4, 2021

FIDO registration of some Authentrend and TrustKey tokens fail with the fido2-net-lib library.

The Authentrend problems that we have had are:

  • AT.Key.Pro USB-C Registered a fingerprint. Failed to register after touching fingerprint reader, stack trace: "Fido2VerificationException: Expected bit string"
    clicking the button instead of registering a fingerprint also caused failure
  • AT.Key.Pro USB-A Failed to register: "Couldn't complete sign-in. Try again and ensure you do the follow-up action" after pressing the button (after time-out). If you touch the fingerprint reader, you get stack trace: "Challenge not equal to original challenge"
  • AT.Key.Card failed to register. After touching fingerprint reader, stack trace: "Fido2VerificationException: Expected bit string"

TrustKey G310H and T110 devices fail FIDO Registration because they have a comma in their DN and fido2-net-lib does not handle commas in DNs correctly.

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

Successfully merging a pull request may close this issue.

1 participant