1Password passkey causes Illegal Invocation error

The problem

Issue aws-samples/amazon-cognito-passwordless-auth#94 (closed, 13 comments): 1Password passkey implementation intercepts webauthn call and replace it with its own implementation in 1Password Chrome extension. The below line in mount the host path https at container path //github.com/aws-samples/amazon-cognito-passwordless-auth/blob/1023e1ef4d2f7eb6b0943315822cecf57f0591d8/client/fido2.ts#L105 causes Uncaught TypeError: Illegal invocation. which results in Illegal invocation shown in the UI when registering fido2 credential. ``` debug?.("Created credential:", { credential, getTransports: response.getTransports?.(), getAuthenticatorData: response.getAuthenticatorData?.(), getPublicKey: response.

What fixed it

[ottokruse (maintainer)]: The Illegal invocation error with 1Password passkeys is an upstream 1Password bug, not this library: Chrome 129 added PublicKeyCredential.toJSON(), and 1Password's proxied credential object breaks on serialization. The reporter confirmed the fault is not with the library. The suggested library-side workaround did not resolve it; report it to 1Password.

In gh:aws-samples/amazon-cognito-passwordless-auth#94 (Amazon Cognito), the issue reported was: Issue aws-samples/amazon-cognito-passwordless-auth#94 (closed, 13 comments): 1Password passkey implementation intercepts webauthn call and replace it with its own implementation in 1Password Chrome extension. The below line in mount the host path https at container path //github.com/aws-samples/amazon-cognito-passwordless-auth/blob/1023e1ef4d2f7eb6b0943315822cecf57f0591d8/client/fido2.ts#L105 causes Uncaught TypeError: Illegal invocation. which results in Illegal invocation shown in the UI when registering fido2 credential. ``` debug?.("Created credential:", { credential, getTransports: response.getTransports?.(), getAuthenticatorData: response.getAuthenticatorData?.(), getPublicKey: response. The verified resolution from the thread: [ottokruse (maintainer)]: The Illegal invocation error with 1Password passkeys is an upstream 1Password bug, not this library: Chrome 129 added PublicKeyCredential.toJSON(), and 1Password's proxied credential object breaks on serialization. The reporter confirmed the fault is not with the library. The suggested library-side workaround did not resolve it; report it to 1Password. Source: mount the host path https at container path //github.com/aws-samples/amazon-cognito-passwordless-auth/issues/94