Windows Hello on local testnet

Is there a workaround to use Windows Hello as an auth for local testnet development?

You can stub out the call to II with Secp256k1KeyIdentity.generate() from @dfinity/identity

1 Like

Thank you, can you please elaborate on your answer.
Which exact call to the II do I have to stub?

If I understand correctly, you would suggest to stub the whole interaction with II locally and use the command you wrote as an alternative to create an identity for the user I can use?

That’s the idea. I haven’t actually done this anywhere yet, though