oddsdk / passkeys Goto Github PK

Currently the demo relies on the PRF extension to handle UCAN signatures and WNFS encryption.
The support for this extension is still limited across devices and browsers, check the following sections to have a better picture of what works and what doesn't.

Auth flows tracking list

• MacOS
  • Chrome using Yubikey ✅
  • Chrome on an Android device (Device Pairing) ✅
  • Chrome on an Android device (QR Code Pairing) ✅
  • Chrome using Touch ID ❌
  • Safari ❌
  • Firefox ❌
• Android
  • Chrome using Device Lock ✅
  • Chrome using another Android device (Cloud Sync) ✅
• iOS
  • Webkit ❌
• Windows
  • 🤷🏻‍♂️

Support

¹ Planned using iCloud.

² No support on the OS level but works directly on Chromium.

³ Behind chrome://flags/#enable-experimental-web-platform-features, doesn't work with CDA.

⁴ Platform authenticator on mac doesnt support it but yubikey does.

References

• Intent to Ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/iTNOgLwD2bI/m/1zKXsF7uAgAJ
• Tracking bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1106961

At some point in the future, can we adapt createComponents so that it doesn't always use the default components, but also respects the custom reference, storage and crypto components I have?

Like so in ts-odd:
https://github.com/oddsdk/ts-odd/blob/main/src/index.ts#L267
(ie. let people pass in their custom components and only if not present in the options param then use the default)