summaryrefslogtreecommitdiff
path: root/storage/innobase/handler/ha_innodb.cc
diff options
context:
space:
mode:
authorDmitry Shulga <dmitry.shulga@mariadb.com>2021-04-12 23:56:12 +0700
committerDmitry Shulga <dmitry.shulga@mariadb.com>2021-04-12 23:56:12 +0700
commit9c7b8ca14cc6076ce37ef559b4de0fc5ed1cb042 (patch)
tree78ea4014056118cd6423109bee6045c0163eafae /storage/innobase/handler/ha_innodb.cc
parentc03841ec0e2b7ac11711243d29821038b26e3edf (diff)
downloadmariadb-git-bb-10.4-MDEV-25197-2.tar.gz
MDEV-25197: The statement set password=password('') executed in PS mode fails in case it is run by a user with expired passwordbb-10.4-MDEV-25197-2
A user connected to a server with an expired password can't change password with the statement "SET password=..." if this statement is run in PS mode. In mentioned use case a user gets the error ER_MUST_CHANGE_PASSWORD on attempt to run the statement PREPARE stmt FOR "SET password=..."; The reason of failure to reset password by a locked user using the statement PREPARE stmt FOR "SET password=..." is that PS-related statements are not listed among the commands allowed for execution by a user with expired password. However, simple adding of PS-related statements (PREPARE FOR/EXECUTE/DEALLOCATE PREPARE ) to the list of statements allowed for execution by a locked user is not enough to solve problems, since it opens the opportunity for a locked user to execute any statement in the PS mode. To exclude this opportunity, additional checking that the statement being prepared for execution in PS-mode is the SET statement has to be added. This extra checking has been added by this patch into the method Prepared_statement::prepared() that executed on preparing any statement for execution in PS-mode.
Diffstat (limited to 'storage/innobase/handler/ha_innodb.cc')
0 files changed, 0 insertions, 0 deletions