Skip to content
This repository has been archived by the owner on Nov 7, 2023. It is now read-only.

[macOS Safari 13 Extension] Registration on Google fails #45

Open
jackdorland opened this issue May 11, 2020 · 11 comments
Open

[macOS Safari 13 Extension] Registration on Google fails #45

jackdorland opened this issue May 11, 2020 · 11 comments

Comments

@jackdorland
Copy link

Hello! It seems when trying to register my Krypton "security key" with Google, it just replies "Remove your security key and try again."

Any insight on what happened?

odd

@agrinman
Copy link
Contributor

Confirmed this is an issue.
Work around: register your key on chrome/firefox, and then it will work in safari for authentication.

Long term, Google doesn't allow u2f registration on safari -- they enforce webauthn only which may need adjustments on the krypton mobile app.

@agrinman agrinman changed the title [macOS Safari 13 Extension] Google doesn't work with Krypton. [macOS Safari 13 Extension] Registration on Google fails May 11, 2020
@agrinman
Copy link
Contributor

Does anyone have a hardware u2f/fido2 key that can test registration on Google?
I have a hunch that registration is broken of Safari for any security key...

@jackdorland
Copy link
Author

I am planning to get one soon... however your workaround worked perfectly. I’ll check back in a while when I make the purchase to see if you still need help.

@agrinman
Copy link
Contributor

I have many, just they are not with me currently :/

@agrinman
Copy link
Contributor

Pretty sure this is a google thing, https://webauthndemo.appspot.com works fine for me (it's a demo built by google). Curious if the hardware token works...

@lumaxis
Copy link

lumaxis commented May 12, 2020

@agrinman I just tested key registration with my Solo key in Safari and it worked just fine.

@agrinman
Copy link
Contributor

@lumaxis you tested registration right?

@lumaxis
Copy link

lumaxis commented May 12, 2020

Yes, sorry. Realized that my comment is a bit ambiguous just after posting. Edited it for clarity 🙂

@agrinman
Copy link
Contributor

Ok thanks, that’s good then! Hopefully they’re not blocking because of something like attestation. Will debug further!

@mkexc
Copy link

mkexc commented May 30, 2020

Ok thanks, that’s good then! Hopefully they’re not blocking because of something like attestation. Will debug further!

Any updates on this? I have this bug too.

@agrinman
Copy link
Contributor

agrinman commented May 31, 2020

Not yet...still an open issue as to why this is happening. In the mean time, I'd suggest registering your krypton key on the chrome browser. Authentication works just fine on Safari.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants