I hope the community is fine, since yesterday I have been presenting a problem with REST and a flow that had been working well, after an hour the error appears
26-Aug-2021 09: 07: 31.145 WARNING [http-nio-8080-exec-18] org.apache.catalina.realm.LockOutRealm.filterLockedAccounts An attempt was made to authenticate the locked user 
when I check the log this is what it shows me
I do not know what I can do or what to check with this user blocking and in the execution the 401 bad request error is presented
Can you expand on what your use case is?
The error you provided indicates that a user has been locked out, usually due to too many failed logins.
Is your workflow call the KNIME Server REST API to do some work and/or return data to another application?
Is your workflow call the KNIME Server REST API to do some work and / or return data to another application?
if he gets me some reports from a database
the problem is that the flow was working fine on the server and then it stopped working.
what data do you need ?
Hi @lizardovanegas , based on the error message, it appears that the user you are using to connect to the REST api is locked.
You need to get the user unlocked, or use another valid user.
Bruno good morning
the issue is that we create another user and try and we keep getting the same error, in case a user is blocked from the knime server how do I unlock it?
Hi @lizardovanegas , this has to be unlocked at the api server. Are you hosting that api, or is that a third party api?
When you say blocked from the Knime server, it’s not entirely clear to me is it’s the Knime server who is hosting the api, or if you are calling a third party api from the Knime server.
a call is being made from knime to an api to execute a flow
Hi @lizardovanegas , yes, we know that a call is being made from Knime to an api, but it’s not answering the question about who is hosting the api. Whoever is hosting the api, or whoever is the admin for the api is who can unlock the user.