I used to be able to use the bitwarden extension to provide my registered Passkey on AWS, but now it does not work anymore as it says “No Passkeys found for this application”.
PS: Bitwarden should allow me to search manually for a specific passkey and provide it.
@barkengineering Welcome to the forum!
Do other passkeys still work?
Do you have Apple’s password app deactivated completely? - I’m not familiar with MacOS, but since some recent posts, I have the impression that Apple’s password app can interfere with Bitwarden heavily.
Is that problem only occuring since yesterday? - If yes, what did you change yesterday with the login item? (it shows so in the screenshot of the item history)
Thank you @Nail1684.
… okay…
You didn’t accidentally get “AWS” on your “excluded domains” list? (Settings → Notifications → Excluded domains)
And just to be sure - you didn’t delete the part of the passkey-pair, that’s stored in AWS?
And that’s a Bitwarden popup stating this?
AWS is not on excluded domains list.
Not sure what you mean by the passkey-pair stored in AWS but no i have not deleted anything on that side.
Actually i tested another AWS account that also has a passkey and the bitwarden popup says the same thing, that it does not find a passkey for this application, when it clearly has one.
Hm, then that more and more looks like a bug with AWS (maybe they changed something on their side?). Either way, you probably should report that (“New issues”) on GitHub.
Passkeys are actually “passkey-pairs”. One part of the pair contains the public key and is stored on the site/server - the other part contains the private key and is stored in an authenticator (like Bitwarden - or on a hardware device). The passkey-pair ceases to work, when one or both parts of the “passkey-pair” are missing.
Why would it be an AWS bug if it’s the extension that says it does not find the passkey ? It’s not that the passkey does not work, I’m sure if i could select and use the passkey, it would work on AWS side.
Created an issue on Github.
Sorry, bad choice of words from me. I meant a Bitwarden bug with the AWS site/passkey. (though I still think it could also be caused by changes AWS made on their side)
We’ll see, if Bitwarden can reproduce the issue.
If another user with a working passkey for AWS could provide which URI they are using with which setting so i can double check mine, that would be very helpful.
