Open kobbe82 opened 6 years ago
OK, we can implement a sleep(60) + retry-login if 403 comes back.
But, are you sure you want to contact lastpass servers in your CI pipeline? You could save the blob and then use --sync=no
for various commands to avoid talking to lastpass servers all the time.
It can be simulated by logging in and out a few times in a row.
In attached the lpass.log file (generated with LPASS_LOG_LEVEL=8) you can see a http 403
The requested URL returned error: 403 Forbidden
We contacted lasspass support and they said:
On the back end, I do see an error just saying that this user is attempting too many logins within 60 seconds. Is this happening more widespread than with this one user? From their activity it looks like they are just logging into the CLI a lot.
Our request to disable a max amount of logins per 60 seconds for a specific user. We need this because we've integrated the lpass-cli in our CI pipeline.