@muhkoo/connect 0.10.7-alpha.0 → 0.10.9-alpha.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -2976,7 +2976,7 @@ function base64UrlDecode(s) {
2976
2976
  * expect (and isn't serving a stale cached bundle). Keep this in sync with
2977
2977
  * `package.json` `version`.
2978
2978
  */
2979
- const VERSION = "0.10.7-alpha.0";
2979
+ const VERSION = "0.10.9-alpha.0";
2980
2980
 
2981
2981
  /**
2982
2982
  * `HttpClient` — the one place the unified {@link Client} talks to the
@@ -3499,7 +3499,13 @@ async function createPasskeyWithPrf(opts) {
3499
3499
  user: { id: rand(16), name: opts.username, displayName: opts.username },
3500
3500
  challenge: rand(32),
3501
3501
  pubKeyCredParams: [{ type: "public-key", alg: -7 }, { type: "public-key", alg: -257 }],
3502
- authenticatorSelection: { residentKey: "preferred", userVerification: "preferred" },
3502
+ // Force the PLATFORM authenticator (Touch ID / Windows Hello / iCloud
3503
+ // Keychain). Our factor needs the PRF extension to wrap the seed, and
3504
+ // third-party browser password-manager extensions register as cross-platform
3505
+ // authenticators that often DON'T implement PRF — letting one handle the
3506
+ // request is the main cause of "didn't return a PRF result" failures. Pinning
3507
+ // to platform routes it to the OS authenticator, which supports PRF.
3508
+ authenticatorSelection: { authenticatorAttachment: "platform", residentKey: "preferred", userVerification: "preferred" },
3503
3509
  extensions: { prf: {} },
3504
3510
  },
3505
3511
  }));