-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"rbw login: failed to log in to bitwarden instance: Username or password is incorrect. Try again." #145
Comments
Also getting this. Been digging in to see if I can figure out if things are going wrong in |
I believe this warning is very warranted, taking into account doy#145. Don't make the same mistake I did...
Same here! |
Same also; this seemed to coincide with my swapping i3 for GNOME, but this issue tells me there is something deeper happening. |
@augustebaum I don't think it's related to a DE/WM, I'm having the same in Plasma connecting to the default API. Maybe BW changed something recently? |
I have this issue with a fresh installation. I can login on both the Chrome extension and the fedora app, yet not with the cli. The only thin I set is the email: |
Was someone able to debug it? I really need rbw in my daily workflow🥲 |
I got the same issue. I tried with default
rbw 1.8.3 |
Same here. Trying
rbw 1.8.3 |
Same here, with the exception that I seem to be able to register with Edit: this is both on a machine where |
I've done some debugging and I think that whilst |
Have tested against |
Until this is fixed I'm using this script to emulate my usage of it, more precisely:
All this based on official CLI client (
just name this script to log in just do a #!/bin/env bash
set -eu -o pipefail
# emulate rbw wit bw
session_path="$HOME/.local/my_local_file"
bwu() {
[ -e "$session_path" ] && source "$session_path"
BW_STATUS=$(bw status | jq -r .status)
case "$BW_STATUS" in
"unauthenticated")
echo "Logging into BitWarden" >&2
export BW_SESSION="$(bw login --raw)"
;;
"locked")
echo "Unlocking Vault" >&2
export BW_SESSION="$(bw unlock --raw)"
;;
"unlocked")
echo "Vault is unlocked" >&2
;;
*)
echo "Unknown Login Status: $BW_STATUS" >&2
return 1
;;
esac
bw sync >&2
echo "export BW_SESSION=\"$BW_SESSION\"" > "$session_path"
chmod 600 "$session_path"
}
if [ "$#" -eq 0 ]
then
echo "Usage: rbw <get|sync> [options] <item>"
exit
fi
case "$1" in
"get")
source "$session_path"
shift
full=0
for arg in "$@"
do
if [ "$arg" = "--full" ]
then
full=1
shift
fi
done
id=$(bw list items --search "$1" | jq -r ".[] | select(.name==\"$1\") | .id")
if [ "$full" = "1" ]
then
json="$(bw get item "$id")"
echo "$json" | jq -r '.login.password' | tail -1
echo "Username: $(echo "$json" | jq -r '.login.username' | tail -1)"
uris="$(echo "$json" | jq -r '.login.uris')"
[ "$uris" != "null" ] && echo "URI: $(echo "$json" | jq -r '.login.uris[].uri' | tail -1)"
else
bw get item "$id" | jq -r '.login.password'
fi
;;
"sync")
bwu
;;
esac |
Has anyone else tested #151 fix? I removed previous version of rbw and installed his revision with the proposed fix, but still getting the error message. |
I've just tested the #151 fix - it does resolve the issue! |
#151 fixes it! yayy!! |
Confirmed, it works |
I might be doing something wrong here, I did and rbw purge, deleted the config file, uninstalled the previous version of rbw, then installed the one from the PR, killed rbw-agent and rebooted my computer, not all at the same time, but that is all what I have done so far and still getting the error message, I checked the cargo checkouts folder and I have the code with the fix in the version installed on my PC. |
@Msouza91 Did your run |
@rjc Register returns 400 as well, after input of the id and secret. |
@Msouza91 Are you a .eu user by any chance? If so, check the issue #148. If not, try on another machine where you previously hadn't used BTW, I've tested on macOS 14.2.1 and OpenBSD -current. |
Regular bitwarden.com user, will try the PBK parameter and rotating keys, thanks for the pointers. |
@rjc I was using Argo2id changed back to PBK, still didn't work for me after rotating keys, I'm at a loss, will try a minimal setup on a VM later and see what happens. |
Try |
@00sapo Well, I only had cargo installed through cargo from the beginning, uninstalled the main version and used the -rev command from the PR to install it again, but didn't work for me, didn't get the time to test on a VM, but it wouldn't change much if it worked on the VM since I can't figure out what is wrong in my main machine. |
It says "rbw 1.8.3 is already installed". Remove it and install or use "--force"... |
Today I noticed that I can no longer log in with rbw. It does not accept my password.
I noticed that others have reported this problem in #32 and #88, though originally those issues were filed for different problems, so I'm creating an issue for this specific problem. Hope this helps.
The text was updated successfully, but these errors were encountered: