@muhkoo/connect 0.10.8-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.
package/dist/browser/index.js
CHANGED
|
@@ -5057,7 +5057,7 @@ function base64UrlDecode(s) {
|
|
|
5057
5057
|
* expect (and isn't serving a stale cached bundle). Keep this in sync with
|
|
5058
5058
|
* `package.json` `version`.
|
|
5059
5059
|
*/
|
|
5060
|
-
const VERSION = "0.10.
|
|
5060
|
+
const VERSION = "0.10.9-alpha.0";
|
|
5061
5061
|
|
|
5062
5062
|
/**
|
|
5063
5063
|
* `HttpClient` — the one place the unified {@link Client} talks to the
|
|
@@ -5580,7 +5580,13 @@ async function createPasskeyWithPrf(opts) {
|
|
|
5580
5580
|
user: { id: rand(16), name: opts.username, displayName: opts.username },
|
|
5581
5581
|
challenge: rand(32),
|
|
5582
5582
|
pubKeyCredParams: [{ type: "public-key", alg: -7 }, { type: "public-key", alg: -257 }],
|
|
5583
|
-
|
|
5583
|
+
// Force the PLATFORM authenticator (Touch ID / Windows Hello / iCloud
|
|
5584
|
+
// Keychain). Our factor needs the PRF extension to wrap the seed, and
|
|
5585
|
+
// third-party browser password-manager extensions register as cross-platform
|
|
5586
|
+
// authenticators that often DON'T implement PRF — letting one handle the
|
|
5587
|
+
// request is the main cause of "didn't return a PRF result" failures. Pinning
|
|
5588
|
+
// to platform routes it to the OS authenticator, which supports PRF.
|
|
5589
|
+
authenticatorSelection: { authenticatorAttachment: "platform", residentKey: "preferred", userVerification: "preferred" },
|
|
5584
5590
|
extensions: { prf: {} },
|
|
5585
5591
|
},
|
|
5586
5592
|
}));
|