Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for roaming authenticator/hardware security key #50

Open
lauravuo opened this issue Feb 2, 2024 · 5 comments
Open

Support for roaming authenticator/hardware security key #50

lauravuo opened this issue Feb 2, 2024 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@lauravuo
Copy link

lauravuo commented Feb 2, 2024

Have you considered to add support for roaming authenticators to ios/android?

When using the javascript webauthn APIs (through iOS webview), a following dialog is shown:
Screenshot 2024-02-02 at 13 11 12
This provides an easy way to use same client code for both passkeys and security keys. However, when using the flutter library, as shown in your example app, there is only the passkeys option.

Thanks anyway for publishing the library, it has helped me greatly with my experiments on flutter and passkeys 👍

@vincentdelitz
Copy link
Contributor

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.

@vincentdelitz vincentdelitz added the enhancement New feature or request label Feb 2, 2024
@J-tt
Copy link

J-tt commented Feb 21, 2024

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.

@vincentdelitz
Copy link
Contributor

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.

@J-tt
Copy link

J-tt commented Feb 22, 2024

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

@J-tt
Copy link

J-tt commented Feb 22, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants