the 10th of december morning, new users couldn't authenticate using IDManager, We've checked the authentication logs. and see Reject reason: locking all the time.
Later, in the afternoon, the same users could auth. normally.
Locking reason appears all days, even when users can access succesfully without problems. ¿What is the meaning of "Locking"?
I think the issue was a temporary down state of the server that authentecates users.
From the 10th, it don't happen again.
Thank you all.
Locking refers to a means of enforcing mutual exclusion when reading or writing to resources.
Think of it as being a synchronisation mechanism for enforcing limits on access to resources in an environment where concurrency takes place.
I suspect that a database was having some backend task or maintenance performed on it, meaning that locks repeatedly couldn't be acquired by ID Manager. After a retry threshold had been met, something like a timeout and/or n attempts, the operations necessary to authenticate a user would fail.
so, it seems like it are runing backend task all the time, isn't it? Locking logs is listed again and again...
This capture is from now and users can auth without problems (i have no notice about, incorrect pass or guest account expirated are not matter).
I would also add that Locking was added due to clients with expired keys continuously requesting authentication, in order to prevent IDM server overload the team added the locout feature to ignore the expired client request in the hopes of improving the database performance.
There are many others to choose from.