-
Notifications
You must be signed in to change notification settings - Fork 1
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
Non working Google U2F authentication on macos app #8
Comments
Hi, just to confirm, are you using the desktop app on MacOS? What does the authentication flow look like with U2F? For my non U2F flow, after I log in it redirects the internal Electron browser to the Google OAuth page. Does U2F cause something to open in another window, or in an actual browser? |
@eric-zeng yes, I'm using the desktop app. The flow is as follow :
|
Ah, I see. The U2F pop-up is still running in Electron (which is running Chromium). But I think the issue is that Electron doesn't support Google's gnubby extension, which enables U2F keys. Brave got around this by forking Electron (see brave/browser-laptop#518) and enabling extension support. I'll look into switching to muon at some point, but for now I'd just recommend using the web version with Chrome. |
Alright ! Thks for your answers, and for your work on Confidante. I like the app very much so far :) |
Hi !
I'm having an issue with confidante on macos.
My Google account uses a hardware second factor to authenticate (FIDO U2F) which works with well Google Chrome, work sometimes with Firefox, and doesn't work at all with Safari. The issue I'm facing is that the webview opened to authenticate on my Google Account is based on Safari, and I can't use my default browser instead. This means confidante can't be used with a secured Google Account :/
The text was updated successfully, but these errors were encountered: