I was indeed successful. And yes, I think displaying more information about the passkey in the BW UI would be great.
I just did some experiments on passkeys.io – not very extensive though – but I couldn’t reproduce so far that no matching passkey was shown.
I think the second thing you mentioned here is already a bit more clear now, as there are two “Save passkey” popups: 1) A passkey already exists… 2) A passkey doesn’t already exist…
The search seems only restricted for case 1) and not case 2). And though I see some reasoning behind the restrictions for case 1) – probably to prevent duplicate passkeys – I also still tend to see that as a bug, as it prevents storing the passkey a) anew / recreating it, b) a second time in the vault or rather in a different login item.
The workaround would probably be to delete the passkey in your BW vault, because then the search begins to function again (case 2) etc. But I wouldn’t delete any important passkey with a good feeling… (of course there should be backups etc.)
That workaround was using the search and clearing it – and so far, I think this only worked for me in my case 2 = no existing passkey already stored. – Does that workaround work for you in my case 1 = Already an existing passkey there… ?
PS: Ah, regarding passkeys.io: did you check, if all your test-passkeys are still valid? One that I created maybe a year ago was not valid anymore (maybe because I didn’t verify the email address?).
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.