Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Currently with the max_password_errors configured, we don't really see any tables having a flag about the blocked user account due to this reason. (i.e., user blocked with the max attempt of trying to connect db with wrong password).
https://mariadb.com/kb/en/server-system-variables/#max_password_errors
One of our customers seems like in requirement of getting the list of blocked users, due to wrong password attempts.
Like for the "Account Locking", whenever a user is locked, will have "account_lock:false or true" in JSON object of the table "mysql.global_priv table", can we implement the similar type of info available for the blocked users for the max_password_errors case?
UPDATE:
The feature request is to have a table like "blocked_accounts" in the information schema which stores all currently blocked (and maybe also locked) accounts and an information why they are blocked. Possible reasons are:
- max-password-errors reached
- max_connect_errors reached
- MAX_CONNECTIONS_PER_HOUR reached (ER_USER_LIMIT_REACHED)
- MAX_USER_CONNECTIONS (ER_TOO_MANY_USER_CONNECTIONS)
- password expired
- account locked
- secure_auth set => mysql_old_password is used
The table content should only be accessible for a user with privilege CONNECTION ADMIN
Attachments
Issue Links
- is caused by
-
MDEV-7598 Block user accounts after failed login attempts
-
- Closed
-
- relates to
-
MDEV-29209 Implement connection response delay after a number of failed login attempts
-
- In Review
-