-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
Can't use Solo V2 with Google #597
Comments
Sorry it is unclear from your post since you mention both "for Google" and "with Microsoft Accounts". What is the relying party you're trying to register a credential on? |
Google.
…On Thu, 13 Jan 2022 at 13:26, Tim Cappalli ***@***.***> wrote:
Sorry it is unclear from your post since you mention both "for Google" and
"with Microsoft Accounts". What is the relying party you're trying to
register a credential on?
—
Reply to this email directly, view it on GitHub
<#597 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABWK6HFL6IGIX2NTRF6NBJTUV47RRANCNFSM5L42R2SA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Wrong repo. See also solokeys/solo2#96 and trussed-dev/fido-authenticator#8. |
Thanks for the pointer @nickray :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Trying to add a new Solo V2 to my keys for Google and it fails with this message:
OS: Windows 11 Pro (Build 10.0.22000)
Browser: Chrome 97.0.4692.71 (Same result in Edge Dev)
Is there any way to get better diagnostics to help troubleshoot this issue?
Side note, it appears to work but fails with Microsoft Accounts but registered successfully for Twitter and GitHub.
The text was updated successfully, but these errors were encountered: