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 PublicKeyCredential" on Safari.It was working before the upgrade without any problem. I didn't change anything except system upgrade. On Firefox it's stil working correctly as before (and Chrome didn't work neither before). Is anybody facing the same problem? Is it problem of Safari 1Password extension?

ShrekyMonster I'm sorry that you're running into the issue as well. There is a known issue with saving passkeys for Oracle Cloud that our development team is tracking, I'll add your report there. For the time being, as a temporary workaround until the issue is fixed I suggest using an alternative method to login or using a different browser to sign in with the passkey. I understand that this isn't ideal and I'm sorry for the disruption. -Dave

Hello branok75! 👋 I'm sorry that you're running into an issue with passkeys in Safari after updating to macOS 15.4. So that I can better understand the situation, can you tell me the following: Are you running into the issue on all websites that you use a passkey to sign into in Safari? Or just a single website? If the issue is only with a single website then can you share the website address of that website? I look forward to hearing from you. -Dave

Hi Dave,thanx for reply.I cannot tell whether it happens on all sites using Passkey in Safari because I don't have any other site where I have to / can use Passkey to login (for test).For me it's a single website where it stopped working. But I cannot share website address as it is our global Corporate SSO login so I don't want to publish it in public forum. :(That's why I'm asking here in this forum whether anybody other is facing this issue - so whether it's only my problem / problem of our corporate login page or whether it's some "general" problem of 1P Safari extension after upgrading to Mac OS 15.4. Brano

branok75 Thank you for the reply. I've done some testing and passkeys in Safari are working for me after I updated to macOS 15.4. Try clearing Safari's browser history/cache to see if that improves things: Clear your browsing history in Safari on Mac If you still see the same issue then we'll need to investigate what's going wrong on your end in more detail. I'd like to ask you to create a diagnostics report from 1Password in your browser:Send a diagnostics report (browser extension)Attach the diagnostics to an email message addressed to support@1password.comWith your email please include: A link to this thread: https://www.1password.community/discussions/1password/passkey-on-safari-results-in-error-publickeycredential-after-upgrade-to-mac-os-1/153962 Your forum username: branok75 You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much! -Dave

Hi Dave,clearing browsing history unfortunately didn't help. I've sent diagnostic report to support.My support ticket ID is : SGT-44933-869. Brano

Passkey on Safari results in error "PublicKeyCredential" after upgrade to Mac OS 15.4

62 Replies

hcubed
New Contributor
20 days ago
Did this get fixed? I signed in this morning and it actually worked.
- branok75
  Occasional Contributor
  20 days ago
  I can confirm, it is working now in Safari again!
  - khaosspawn
    Dedicated Contributor
    20 days ago
    Same - Safari and Brave both work for me now!
    Can someone please let us know what the status is? It would be very unfortunate if this were to just stop tomorrow (for example).
nitseee
New Contributor
27 days ago
I am also running into exactly same issue, can't login to OracleCloud because of this error.
- nitseee
  New Contributor
  27 days ago
  Just solved it :cheers:
  If anyone running into this issue, here's how I solved it.
  Login to same 1Password on your iphone > Use Safari to login to Oracle Cloud > 1Password should pop-up saying passkey available > It should work > Reset MFA on Profile/Security.
  - ziggie216
    New Contributor
    27 days ago
    Oracle accounts with iOS safari and 1P works fine. It’s macOS Safari that we’re having issue with.
andre30
New Contributor
31 days ago
Hello,
As a paying customer, I would expect a more professional response and timely resolution. The issue first appeared in early November 2024. I am certain this is on your side, as it was identified internally at the time.
I understand how support and development processes work, but it should not take a full year to resolve a problem of this nature. For your customers, being unable to access Oracle sites (and potentially others) is highly discouraging.
You may consider it “just one site,” but for me it represents 70% of my daily logins. Open-source alternatives have already resolved this issue.
This is not personal to anyone on your team, but I ask sincerely: would you accept this level of support if you were in my position?
With all honesty,
Andreas
- 1P_Dave
  Moderator
  26 days ago
  andre30
  
  I'm sorry for the continued frustration. This is something that our development team is working on a fix for but there are a few different moving pieces that have delayed the fix being ready for release. Hopefully we'll have an update to share soon.
  
  For the time being, you should be able to use a different sign-in method until the passkey issue is resolved.
  
  -Dave
  - andre30
    New Contributor
    26 days ago
    Hi Dave,
    This is exactly what I’ve been doing over the past year. Recently, I’ve been using the workaround shared here:
    https://github.com/bitwarden/clients/issues/12060#issuecomment-2668801199
    But for a seamless experience? Not even close. Sure, I could just use iCloud or Chrome passkeys—so in that case, what’s the point of using 1Password?
    
    For some sites (oracle SSO), passkeys are the only allowed login method and I cannot blame them trying to promote security.
    
    Thanks
    A
- slessard
  New Contributor
  31 days ago
  Andreas has captured my frustrations perfectly. I am completely frustrated that 1Password hasn't shown any progress on this issue.
pepano
New Contributor
2 months ago
Hello,
I’ve run into an issue with using passkeys stored in 1Password when signing in to Oracle Single Sign-On from Safari on macOS.
macOS version: Sequoia 15.6.1
Safari version: 18.6
1Password app version: 8.11.6
1Password Safari extension: enabled
Steps to reproduce:
Generate and store a passkey for Oracle SSO using Firefox on macOS (works fine).
Open the Oracle SSO login page in Safari.
1Password correctly offers the saved passkey.
After selecting the passkey, the login flow fails with the following error in the console:
TypeError: Can only call PublicKeyCredential.toJSON on instances of PublicKeyCredential
Expected behavior:
The saved passkey should authenticate successfully in Safari, just as it does in Firefox.
Actual behavior:
Safari shows the error above and login fails.
Notes:
The same passkey works correctly in Firefox (both creation and login).
In Safari, it looks like the Oracle page expects a native PublicKeyCredential object, but 1Password’s bridge is returning something different.
This makes Oracle SSO unusable with passkeys via Safari + 1Password.
Could you please confirm if this is a known compatibility issue with Safari and if there’s a workaround?
Thanks!
- 1P_Dave
  Moderator
  2 months ago
  pepano
  
  I'm sorry that you've run into an issue using passkeys with Oracle's website. This is a known bug and I've merged your post into the existing thread.
  
  The issue is currently open with our development team and we hope to release a fix in the future.
  
  -Dave
  
  Issue=FS-828
ziggie216
New Contributor
3 months ago
Been dealing with this error for almost a year and it's really bugging me that this hasn't been resolved. My current option is to 1) Use Firefox w/ 1P or 2) use iCloud Keychain for specially this Oracle passkey login. On macOS 26 now and nothing has changed.
- 1P_Dave
  Moderator
  3 months ago
  I'm sorry that the issue is disrupting your workflow with Oracle. I've added your report to the internal work item for the issue.
  
  -Dave
  
  #33167
slessard
New Contributor
5 months ago
This is a really sad response from 1Password. To be fair 1Password isn't the only password manager with this bug. The major difference is that other password managers are fixing the issue. Bitwarden has this same bug and the fix on the way. I sure wish 1Password would get it together and fix this bug.

https://github.com/bitwarden/clients/issues/12060
https://github.com/bitwarden/clients/pull/14734
- 1P_Dave
  Moderator
  5 months ago
  slessard
  
  Thank you for this information, it's very helpful. I've shared this with the team internally.
  
  Out of curiosity, did you try the suggestion mentioned here on the page that you linked to and did that allow 1Password to save or sign in using a passkey?
  
  -Dave
  - branok75
    Occasional Contributor
    5 months ago
    I can confirm, when I run in Safari Development Mode Console "delete PublicKeyCredential.prototype.toJSON" before clicking on button "Verify Passkey on device <my_device_name>", then clicking on it -> 1Password's "Sign-in with Passkey" popup appeared, again clicking on it (confirmed on phone) and everything worked as before - I logged in successfully.
- khaosspawn
  Dedicated Contributor
  5 months ago
  Hi 1P_Dave - please can we have some timelines on when this will be fixed. I have to do some really weird "scaning a QR code with my phone" work arounds to login to Oracle sites because 1password doesn't handle this toJSON function properly.
  I've been using 1password since Version 4 in 2013 and I've never seen 1Password sit on this serious an issue for 6 months. Please at least communicate to us when this is scheduled. As more companies go passwordless, and insist on passkeys - this is going to lock people out!
  
  If the answer keeps being - well use some other browser, use another method - then why am I using 1password? This is such a disappointment from the early days where serious issues like this would be communicated well.
  Please help us!
branok75
Occasional Contributor
5 months ago
1P_Dave Hi Dave, still no solution/fix to this problem? :(
- 1P_Dave
  Moderator
  5 months ago
  The issue is currently open in our team's backlog, hopefully it can be addressed soon. While I can't provide an ETA on when the issue will resolved, this is something that our team is aware is in need of fixing.
  
  For the time being, trying using an alternate sign-in method as a workaround. Some customers have also reported success with passkeys when using Firefox which might be an option if you're willing to use another browser for the website in question.
  
  I'm sorry for the continued inconvenience.
  
  -Dave
  
  #33167
khaosspawn
Dedicated Contributor
6 months ago
Any update on the issue? A lot of companies use Oracle IDCS to authenticate and not being able to use 1P in our preferred browsers is a huge headache.
- branok75
  Occasional Contributor
  6 months ago
  No, no update, stil not working ... :(
slessard
New Contributor
7 months ago
My support ticket ID is DMX-16382-353.
- 1P_Dave
  Moderator
  7 months ago
  slessard
  
  Thank you! One of my colleagues will send you a reply via email soon.
  
  -Dave
slessard
New Contributor
7 months ago
I have the same problem.
I have confirmed passkey authentication is broken in:
Safari Version 18.4 (20621.1.15.11.10)
Brave Version 1.77.97 Chromium: 135.0.7049.84 (Official Build) (arm64)

I have confirmed passkey login still works with Friefox 137.0.1 (aarch64)
ProductName: macOS
ProductVersion: 15.4
BuildVersion: 24E248
Darwin 24.4.0 Darwin Kernel Version 24.4.0: Wed Mar 19 21:17:32 PDT 2025; root:xnu-11417.101.15~1/RELEASE_ARM64_T6030 arm64
Apple M3 Pro