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 immediately receive a Failed to Enter Correct Password error, and can confirm it's an actual failure (as evidenced by my locking the account temporarily after several failed attempts in a short time).
At first I thought the pipe was having an issue with not escaping a character correctly. However, echo [PASSWORD] | cat displays the password just fine, and even using a different account with a password that is only alphanumeric characters still does not work.
Trying echo [PASSWORD] | lpass login --trust email@domain.com also does not work.
All of the results I found both here on Issues as well as general searching generally point to Linux installs. Is there something specific to the Windows distribution that I'm overlooking, or formatting incorrectly?
The text was updated successfully, but these errors were encountered:
Similar to #597 I am trying to automate the Lastpass CLI login process, Our installation is running on a Windows 2012 R2 Server.
We have set environmental variable
LPASS_DISABLE PINENTRY = 1
and then per https://stackoverflow.com/questions/64086272/how-to-automate-the-lastpass-cli-login-process I have executedecho [PASSWORD] | lpass login email@domain.com
I immediately receive a
Failed to Enter Correct Password
error, and can confirm it's an actual failure (as evidenced by my locking the account temporarily after several failed attempts in a short time).At first I thought the pipe was having an issue with not escaping a character correctly. However,
echo [PASSWORD] | cat
displays the password just fine, and even using a different account with a password that is only alphanumeric characters still does not work.Trying
echo [PASSWORD] | lpass login --trust email@domain.com
also does not work.All of the results I found both here on Issues as well as general searching generally point to Linux installs. Is there something specific to the Windows distribution that I'm overlooking, or formatting incorrectly?
The text was updated successfully, but these errors were encountered: