authentication errors detection - how it detects authentication is faulty or ok

[lukasdebaum]

Hi

I have the problem that when I run the replication-manager-cli several times I get "blocked" for 3 minutes.

root@ha-c1:~# replication-manager-cli status --user root --password xxx
running
root@ha-c1:~# replication-manager-cli status --user root --password xxx
running
root@ha-c1:~# replication-manager-cli status --user root --password xxx
running
root@ha-c1:~# replication-manager-cli status --user root --password xxx
INFO[0000] ERROR in login unexpected end of JSON input  

replication-manager-osc monitor 3 authentication errors for the user root, please try again in 3 minutes

How does the following function (server/api.go) decide if the authentication is faulty or ok? and only count if the authentication is faulty. 565e82b

[svaroqui]

Hi thanks for reporting That's a new feature , are you sure that the authentification is valid this feature is anti brut force attack but the login counter should not increase on success

[lukasdebaum]

I think so I get data back ("running")

root@ha-c1:~# replication-manager-cli status --password xxx
running
root@ha-c1:~# replication-manager-cli status --password yyy
Cluster not found

Is my problem not reproducible if you check the "status" more than 3 times in a short time?