Support for roaming authenticator/hardware security key about flutter-passkeys HOT 5 OPEN

Hey @lauravuo,

Thanks for raising this issue!

In the current implementation, we intentionally omitted the security key (roaming authenticator) option. This decision was based on our experience, as it often led to confusion among non-technical users. However, we are currently revamping our device and passkeys management in our hosted backend and plan to incorporate a feature toggle that will enable you to provide security keys as an option. This will also necessitate an update to the Flutter package, allowing you to offer security keys as well.

I'll keep you posted / update this GitHub issue as soon as there are any news.

from flutter-passkeys.

I made a very rough workaround to support just hardware keys (applying this patch will mean you can't use normal passkeys).

You can then override just the passkey_ios dependancy in your flutter pubspec.yaml to a local copy.

0001-Replace-mentions-of-Platform-with-SecurityKey.patch

from flutter-passkeys.

Hi @vincentdelitz any updates on this?

It's a make or break option for this library for us, even if there's a workaround or patch we can apply that'd be fantastic.

from flutter-passkeys.

Hi @vincentdelitz any updates on this?

It's a make or break option for this library for us, even if there's a workaround or patch we can apply that'd be fantastic.

Hey @J-tt,
Would you use your own relying party server or a Corbado-hosted one?
In general, this feature is still under development, maybe I can provide a workaround though.

from flutter-passkeys.

@vincentdelitz were using our own server, it's an internal facing app so there's less concern about user confusion.

from flutter-passkeys.