[GH-ISSUE #36] Add support for Google accounts with security keys #35

Closed
opened 2026-03-02 23:33:09 +03:00 by kerem · 2 comments
Owner

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.

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.
kerem closed this issue 2026-03-02 23:33:09 +03:00
Author
Owner

@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?

<!-- gh-comment-id:1364159485 --> @tagavari commented on GitHub (Dec 23, 2022): On macOS 10.15 or later, AirMessage Server 4 uses [ASWebAuthenticationSession](https://developer.apple.com/documentation/authenticationservices/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](https://support.google.com/accounts/answer/6103523?hl=en&co=GENIE.Platform%3DDesktop&oco=2) 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?
Author
Owner

@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 :)

<!-- gh-comment-id:1382903757 --> @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 :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/airmessage-server#35
No description provided.