mirror of
https://github.com/airmessage/airmessage-server.git
synced 2026-04-26 01:05:50 +03:00
[GH-ISSUE #36] Add support for Google accounts with security keys #35
Labels
No labels
bug
enhancement
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/airmessage-server#35
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @StevenPrescott on GitHub (Dec 23, 2022).
Original GitHub issue: https://github.com/airmessage/airmessage-server/issues/36
Right now, you can't sign into a Google account that uses security keys because the in-app browser on Mac doesn't support them in AirMessage. Additionally, with Advanced Protection enabled there is no bypass other than removing and re-enrolling all your keys.
Rather than using the alternative iMessage setup method, it would be nice if the app could either: show the URL (so the user can copy it into their own browser that does support security keys) or be given the option to complete the sign-in directly in their browser.
@tagavari commented on GitHub (Dec 23, 2022):
On macOS 10.15 or later, AirMessage Server 4 uses ASWebAuthenticationSession, which uses Safari by default, or the user's default browser if it supports web authentication sessions. I believe Chrome and Edge support this feature.
On macOS 10.14 or earlier, AirMessage Server 4 will launch the default browser.
Google's support page on security keys says that security keys are supported on Chrome, Firefox, and Safari.
I haven't tested AirMessage with an account protected by a security key, though the documentation implies this should work in practice. Can you explain how what you're experiencing differs from my understanding of how the process should work?
@StevenPrescott commented on GitHub (Jan 14, 2023):
Sorry for the late reply. I went back and tried again. This time the login with Google option opened in a Safari window that supports keys. Closing this issue :)