LineageOS 21: Bitwarden cannot be used for passkey authentication on mobile about mobile HOT 9 OPEN

Sorry, I forgot to mention the tested apps:

• Vivaldi mobile browser (v.6.7.3335.149)
• Firefox mobile browser (v.127.0)
• Chrome mobile browser (v.126.0.6478.71)

Additionally, I followed the documentation and enabled flag "M124", but no avail.

Addition:
At first I did not find the second option (Enabled for 3rd party passkey providers under Android Credential Management for passkeys). After a closer look I found and enabled it. Now, the Chrome browser shows a bitwarden prompt when authenticating at "webauthn.io", but throws the following error message:

Fehler beim Lesen des Passkeys. Es gab ein Problem beim Lesen deines Passkeys für webauthn.io. Versuche es später erneut

Since my LineageOS smartphone is rooted. Are there any log files I could inspect?

from mobile.

@somova Do you know if LineageOS supports Google Play Services?

Yes, all my OnePlus phones with LineageOS 21 have Google Play Services installed.

from mobile.

Hi @somova,

Thank you for this report. Did you test this in Chrome after performing the steps that are outlined in the documentation?

Thank you in advance,

from mobile.

@somova Do you know if LineageOS supports Google Play Services?

from mobile.

@somova Do you know if LineageOS supports Google Play Services?

Yes, LineageOS supports Google Play Services. During initial installation phase of LineageOS the user can decide to add the Google addon package. On my smartphone Google Services including Google Play are available

from mobile.

Now authentication succeeds with the Chrome browser. The error message

Fehler beim Lesen des Passkeys. Es gab ein Problem beim Lesen deines Passkeys für webauthn.io. Versuche es später erneut

disappers if the session timeout in the bitwarden mobile app is set to a value other than "immediately". Registering a passkey is still not offered.

from mobile.

I don't think this is a LineageOS-specific issue. I similarly can't create passkeys using a more mainstream setup:

• Operating System: Android
• Operating System Version: Android 14 (Build number: AP2A.240605.024)
• Device: Pixel 6a (Hardware version: MP1.0)
• Build Version: 2024.6.0 (10746)

I tried with the following browsers:

• Chrome (com.android.chrome): version 126.0.6478.122
  • The setting under chrome://flags was called "Enabled for 3rd party passkeys" instead of "Enabled for 3rd party passkey providers", which what the Bitwarden documentation states
• Firefox (org.mozilla.firefox): version 128.0 (Build #2016030615)

In both browsers, when I tried to create a passkey for https://webauthn.io/, Google's password manager popped up instead as the only option for storage. Additionally, when I created an account for https://webauthn.io/ on my desktop, I was able to use that account to log in for both Chrome and Firefox.

I was unable to use Bitwarden when I attempted to log into an existing account on a website, but I think it is related to the following limitation (from Setup Bitwarden for use with passkeys):

Please also note that Android does not allow 3rd party passkey providers like Bitwarden to support passkey-based 2FA (a.k.a. "non-discoverable credentials").

from mobile.

I've just submitted a suggestion to that article.

Perhaps youve got the same issue.

On my CMF Phone I've got the additional field 'Additional Providers' in the relevant android settings.

When I unselected the only option, google, there, it did not offer to save passkeys in google any longer. But any Passkey registration simply failed.

I had to switch the regular option to none and then back to bitwarden (after unselecting google in the additional option of course) to make bitwarden offer to save passkeys when registering them.

from mobile.

Are there any news in this topic?

from mobile.