Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Passkey on Safari results in error "PublicKeyCredential" after upgrade to Mac OS 15.4
Hi all, after upgrading to Sequoia 15.4, authentication using Passkey (which is required by my employer) ends with error message "TypeError: Can only call PublicKeyCredential.toJSON on instances of P...
1P_Dave
Moderator
Moderatorslessard, hcubed, branok75, khaosspawn
I've checked the internal work item open to fix this and our development team's work is still ongoing. The issue is still open with our development team and other customers have reported that they still experience issues with passkeys on Oracle's website.
I've left a note with our development team to let them know that passkeys are working for you on Oracle's website and I'll reach out if there's any information that our development team asks for from your end. If the issue returns for you then let me know.
-Dave
edit: Edited for clarity.
Issue=FILL-493
Issue=FS-233
As with andre30 I wanted to add that I am still experiencing the issue as originally reported. Although since then I'm now on macOS 26.1 and Safari 21622.2.11.11.9.
It does amuse me every time I see Oracle and 1Password on the Red Bull Racing Formula 1 cars... perhaps having your two brands on the same car might cause people to expect them to work together! 😉
ShrekyMonster that is weird because I am running the same versions of macOS and Safari and things work for me logging into my cloud.oracle.com tenancy. It works on Safari, Brave and Chrome.
It is weird!
I thought maybe if I deleted the passkey and tried to add it back again that might work, alas, I get taken to the profile page to add it but I immediately get the same error, on attempting to create the key.
TypeError: Can only call PublicKeyCredential.toJSON on instances of PublicKeyCredentialThe odd thing is, it does store a key, but this time Oracle does not acknowledge the passkey so it continues to show as "Not Configured". Just mentioning this in case it helps the 1Password dev team debug things further, but cannot believe this isn't one of the simpler fixes to make (of course a dangerous assumption given I know nothing of the codebase).
Chrome just gives me TypeError: Illegal invocation.
If I repeat the same steps via Firefox it registers the key and the key works when using Firefox, but of course not Safari/Chrome.
Hey Dave
I'm not sure where you're getting your information from. This is not fixed. Easy to test: any Oracle cloud login fails with exact same issue.
Oracle SSO for oracle sites seems to be working but the rest, no change.
Also I'm not sure what you mean development is working on.... One year seems a lot of time to fix a bug.
I encourage you to take serious action and not hope on a self-fix.
If you believe it cannot be fixed, drop us a line and I will stop my subscription to save all of us some time and inform also other colleagues waiting (guess where we work).I can take any argument but this has gone way too far for a paid service
- 1P_Dave
My earlier message was meant for the four community members who had previously reported, in this thread, that they were no longer experiencing the issue. Please rest assured that the internal bug report remains open with our development team.
-Dave
I think any chromium based browser has this issue.
Firefox works.
Safari gives:
TypeError: Can only call PublicKeyCredential.toJSON on instances of PublicKeyCredential
Chrome gives:
TypeError: Illegal invocation
This happens on any https://cloud.oracle.com/ tenancy.
But not for sites like support.oracle.com.
Anyway, I do not know how Firefox differs from chromium browsers but certainly handles passkeys differently.
And last but not least, other password managers (keychain, chrome etc) work without issues.
