You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have created a FIDO2 passkey, which is saved to Bitwarden and key properties stored in multifactor_userkey table.
When posting to /mfa/multifactor/fido2/begin-auth/, authenticate_begin calls get_user_credentials, which attempts to find UserKey object with properties__domain equal to request.get_host().
I don't know if this is an issue specific to Bitwarden, but the saved FIDO2 key has properties__domain equal to localhost. When working with localhost, the request.get_host() will return the port as well: localhost:8000. This causes a mismatch that doesn't return an AttestedCredentialData object, and Bitwarden states "No passkeys found for this application."
Simply changing the line to properties__domain=request.get_host().split(":")[0] solves the issue and Bitwarden can now find the passkey.
The text was updated successfully, but these errors were encountered:
Similar to #70:
I have created a FIDO2 passkey, which is saved to Bitwarden and key properties stored in
multifactor_userkey
table.When posting to
/mfa/multifactor/fido2/begin-auth/
,authenticate_begin
callsget_user_credentials
, which attempts to findUserKey
object withproperties__domain
equal torequest.get_host()
.I don't know if this is an issue specific to Bitwarden, but the saved FIDO2 key has
properties__domain
equal tolocalhost
. When working withlocalhost
, therequest.get_host()
will return the port as well:localhost:8000
. This causes a mismatch that doesn't return anAttestedCredentialData
object, and Bitwarden states "No passkeys found for this application."Simply changing the line to
properties__domain=request.get_host().split(":")[0]
solves the issue and Bitwarden can now find the passkey.The text was updated successfully, but these errors were encountered: