Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Hiroyuki
7 months agoNew Contributor
Issues with PublicKeyCredential: toJSON() and passkeys
We are developing a SaaS service with passkey support.
When we tested passkey functionality with 1Password across various browsers, we found that it is completely broken.
Does 1Password offer any support for SaaS developers integrating passkeys?
The specific issues are as follows:
Chrome Extension
When using 1Password as the authenticator, calling PublicKeyCredential: toJSON() to convert the authenticatorResponse into JSON for sending to the server results in an error, as this method no longer works.
Firefox Extension
When using 1Password as the authenticator, PublicKeyCredential: toJSON() can be executed to convert the authenticatorResponse into JSON, but the result ignores ArrayBuffer, causing attestationObject, clientDataJSON, etc., to be blank.
5 Replies
- jtrubaNew Contributor
I've opened a support case VLR-95342-737 about this as well: the browser extension consistently breaks `toJSON` across multiple browsers.
In Chrome, `PublicKeyCredential#toJSON()` and `JSON.stringify(PublicKeyCredential)` both result in "TypeError: Illegal invocation".
In FireFox, `PublicKeyCredential#toJSON()` gets "TypeError: result.toJSON is not a function", while `JSON.stringify(...)` results in ArrayBuffer members being serialized incorrectly.
This all goes away if the extension is disabled.
- rentectravisNew Contributor
I also am encountering this problem. I emailed mailto:support@1password.com with the info requested. Support ticket ID: PGH-46889-373.
Crazy that in 2026 web developers still have to use a polyfill https://github.com/github/webauthn-json/tree/main - 1P_Dave
Moderator
Hello Hiroyuki​! 👋
I'm sorry that 1Password is running into issues with passkey functionality in certain circumstances. It sounds like you're running into a known issue that the team has noted on at least one other website. So that we can gather more information from your end, can you reproduce the issue again and send in a diagnostics report:
Send a diagnostics report (browser extension)
Attach the diagnostics to an email message addressed to support@1password.com
With your email please include:- A link to this thread: https://www.1password.community/discussions/1password/issues-with-publickeycredential-tojson-and-passkeys/158327
- Your forum username: hiroyuki
- The website address of the affected webpage.
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!-Dave
#33167
- langalexNew Contributor
We are running into the same/a similar issue. On Firefox, PublicKeyCredential#toJSON does not exist. When calling `JSON.stringify(credential)` without calling `toJSON()`. the attestationObject, clientDataJSON, etc are blank as described above.
- 1P_Dave
Moderator
I'm sorry that you're being affected by the same issue. Can you share the address of the website where you're running into the issue so that I can pass that along to our development team?
-Dave
Issue=FS-233