This patch adds the `reset_last_active` subcommand to the
`keystone-manage` command line tool.
This subcommand will update every user in the database that has a null
value in the `last_active_at` property to the current server time. This
is necessary to prevent user lockout in deployments that have been
running for a long time without `disable_user_account_days_inactive` and
later decide to turn it on.
This patch also includes a change to the logic that sets
`last_active_at` to fix the root issue of the lockout.
Closes-Bug: 2074018
Change-Id: I1b71fb3881dc041db01083fbb4f2592400096a31
(cherry picked from commit e9513f8e4f25e1f20bc6fcab71d9177120000abf)
Reviewed: https:/ /review. opendev. org/c/openstack /keystone/ +/925920 /opendev. org/openstack/ keystone/ commit/ 62b3c9260b79b95 96545debbd7e4fc d3b4eab972
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/2024.1
commit 62b3c9260b79b95 96545debbd7e4fc d3b4eab972
Author: Douglas Mendizábal <email address hidden>
Date: Fri Jul 19 17:10:11 2024 -0400
Add keystone-manage reset_last_active command
This patch adds the `reset_last_active` subcommand to the manage` command line tool.
`keystone-
This subcommand will update every user in the database that has a null user_account_ days_inactive` and
value in the `last_active_at` property to the current server time. This
is necessary to prevent user lockout in deployments that have been
running for a long time without `disable_
later decide to turn it on.
This patch also includes a change to the logic that sets active_ at` to fix the root issue of the lockout.
`last_
Closes-Bug: 2074018 1db01083fbb4f25 92400096a31 20bc6fcab71d917 7120000abf)
Change-Id: I1b71fb3881dc04
(cherry picked from commit e9513f8e4f25e1f