Is your feature request related to a problem? Please describe.
Since 0.3.14 microG handles incoming FIDO:/ hybrid (caBLE) requests correctly — the tunnel is established and the flow completes. However, the credential is only sourced from microG's own passkey store.
Passkeys stored in a third-party Credential Manager provider (tested with Proton Pass, set as the system's default passkey provider) are never offered. This makes cross-device authentication unusable for users who keep their passkeys in a syncing password manager, which is arguably the main reason to have a third-party provider at all.
Describe the solution you'd like
After the hybrid handshake, query the Credential Manager providers the user has enabled instead of only microG's internal store — ideally via the normal provider selection UI, so any provider works without
per-app support.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Is your feature request related to a problem? Please describe.
Since 0.3.14 microG handles incoming FIDO:/ hybrid (caBLE) requests correctly — the tunnel is established and the flow completes. However, the credential is only sourced from microG's own passkey store.
Passkeys stored in a third-party Credential Manager provider (tested with Proton Pass, set as the system's default passkey provider) are never offered. This makes cross-device authentication unusable for users who keep their passkeys in a syncing password manager, which is arguably the main reason to have a third-party provider at all.
Describe the solution you'd like
After the hybrid handshake, query the Credential Manager providers the user has enabled instead of only microG's internal store — ideally via the normal provider selection UI, so any provider works without
per-app support.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context