mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #298] Cannot log in from Android when 2FA is enabled #158
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#158
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aksdb on GitHub (Dec 16, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/298
In the current version of bitwarden_rs, I can no longer login with the Bitwarden Android client with accounts that have 2FA enabled. The app immediately closes.
Since my Android development setup is still kinda sucky (or I suck at using it :-)) the only thing I got out of the debugger was "System.InvalidOperationException: Token not found." without a proper stacktrace.
I presume something in the response is missing. Or maybe simply the casing of the key(s) is different? Apparently it works in the jslib implementation, so it has to be something that the C# implementation of the mobile apps does differently.
@tycho commented on GitHub (Dec 16, 2018):
I've run into this as well. The log for bitwarden_rs claims the login attempt succeeded, but the Android app really didn't like whatever response bitwarden_rs gave.
@dani-garcia commented on GitHub (Dec 16, 2018):
You were right, it was because of a casing issue. That was solved some time ago for the JSON API. But the login is a normal form instead. It should be fixed now in the latest master, tested on iOS.
@mprasil commented on GitHub (Dec 16, 2018):
Image from master is now building. Give it about an hour.
@tycho commented on GitHub (Dec 17, 2018):
@dani-garcia Confirmed, that fixed it!
@aksdb commented on GitHub (Dec 17, 2018):
Thanks @dani-garcia (and @mprasil) for getting a fix out that fast. Works fine now :-)