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
{{ message }}
This repository has been archived by the owner on Nov 7, 2023. It is now read-only.
I've been successfully using Krypton for over a year, but one thing I've noticed is that it almost never works the first time. eg I go to log into a webauthn site, the site asks me to "click the token" and I stare at my phone waiting for Krypton to trigger... and I wait... and I wait... and nothing happens. I then cancel the webauthn process in the browser, then try again - and it almost always works the second time
I suspect this is something to do with your use of AWS SQS? The queuing is maybe a bit "best effort"?
I see this on both Firefox and Chrome - so I don't think it's browser-related, and obviously I don't ever see this issue if I use a USB-based webauthn key
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've been successfully using Krypton for over a year, but one thing I've noticed is that it almost never works the first time. eg I go to log into a webauthn site, the site asks me to "click the token" and I stare at my phone waiting for Krypton to trigger... and I wait... and I wait... and nothing happens. I then cancel the webauthn process in the browser, then try again - and it almost always works the second time
I suspect this is something to do with your use of AWS SQS? The queuing is maybe a bit "best effort"?
I see this on both Firefox and Chrome - so I don't think it's browser-related, and obviously I don't ever see this issue if I use a USB-based webauthn key
The text was updated successfully, but these errors were encountered: