Rado

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 🙂

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.

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.

I also observe this behavior. It is really annoying. I can say that it happens only after unlock. If Enpass has been already unlocked, the Assistant keeps the results filtered by URL. But if I lock it and then close it, and then reopen and unlock it, initially I see the item I need for the current website and immediately after that the results get refreshed and I see "Most recent items". I need to close and reopen the Assistant again in order to see the correct item listed.