May 5May 5 I tried to save a passkey to Enpass from Chase in Firefox. When I attempt to save the passkey, I get"It looks like something went wrong. Try adding a passkey again."So far, I have:Tried this on a different brower like Brave with enpass extension. The same thing happened.Tried this on a different password manager, in this case Bitwarden and the passkey was saved in firefox and Brave.In either case, the extension was configure to save passkeys.Tried on MacOS, Linux, and Windows. Edited May 5May 5 by paulsiu
May 6May 6 I also have the same problem. Could be an issue on Chase's side, because I also tried creating a passkey through their Android app and I don't even see the "Add passkey" button there, even though it says that I can add and delete them through there.Update:I have tested disabling Enpass as passkey handler and leaving only the native Windows passkey manager, but I got the same results both with Brave and Firefox. This makes me believe again that the problem is on Chase's side. Edited June 12Jun 12 by Rado
July 6Jul 6 Author Note that I am able to successfully save chase passkey to apple keychain, but not to enpass.
July 8Jul 8 I just found some time to dig into the problem. It seems that Chase requires only hardware (platform) authenticators, like Windows Hello or Apple Keychain, and is blocking any cross-platform (software) ones. Here is the error I get when Enpass handles the passkeys:"Unsupported AAGUID:f3809540-7f14-49c1-a8b3-8f813b225541"That is the authenticator ID of Enpass.I was able to make Chase's passkeys work only with Windows Hello (not Microsoft Password Manager) on my Windows 11 PC.So, bottom line is this is a restriction on the Chase's side and Enpass can't do anything to change it, unfortunately. I have seen this on other sites and it is very annoying.
July 9Jul 9 Thanks Rado for clarifing this issue. I saw this aswell with other websites but never figured, it was a restriction from their side. What an annoyance.
July 9Jul 9 Author On 7/8/2026 at 1:20 PM, Rado said:I just found some time to dig into the problem. It seems that Chase requires only hardware (platform) authenticators, like Windows Hello or Apple Keychain, and is blocking any cross-platform (software) ones. Here is the error I get when Enpass handles the passkeys:That is the authenticator ID of Enpass.I was able to make Chase's passkeys work only with Windows Hello (not Microsoft Password Manager) on my Windows 11 PC.So, bottom line is this is a restriction on the Chase's side and Enpass can't do anything to change it, unfortunately. I have seen this on other sites and it is very annoying.If chase require device bound keys how does it work with Apple keychain, which is not device bound?
July 10Jul 10 10 hours ago, paulsiu said:If chase require device bound keys how does it work with Apple keychain, which is not device bound?I am not a Mac user so I'm not really familiar with the terminology there, but as far as I know, Apple Keychain stores the passkey in the Secure Enclave (which is the hardware component) and this way it matches the requirement for a platform authenticator. Hopefully the Mac experts can correct me if I'm wrong here ๐
Create an account or sign in to comment