From 483a8196d67bf374dc15f7f4c1fa176c2d74e8be Mon Sep 17 00:00:00 2001 From: Elisamara Aoki Goncalves Date: Tue, 7 Dec 2021 16:17:17 -0300 Subject: [PATCH] Service parameters deprecated and not being used by puppet manifests Applied formatting changes Closes-bug: 1950490 Signed-off-by: Elisamara Aoki Goncalves Change-Id: Iaae1f1d93cc2c3be993781b0d1250b4214148d16 --- ...-horizon-user-lockout-on-failed-logins.rst | 20 +++++++++---------- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git a/doc/source/security/kubernetes/configure-horizon-user-lockout-on-failed-logins.rst b/doc/source/security/kubernetes/configure-horizon-user-lockout-on-failed-logins.rst index e7c9e6838..7de579844 100644 --- a/doc/source/security/kubernetes/configure-horizon-user-lockout-on-failed-logins.rst +++ b/doc/source/security/kubernetes/configure-horizon-user-lockout-on-failed-logins.rst @@ -19,8 +19,8 @@ user must wait before the lockout is reset. sessions, perform this procedure during a scheduled maintenance period only. -By default, after three consecutive failed login attempts, a user must wait -five minutes \(300 seconds\) before attempting another login. During this +By default, after five consecutive failed login attempts, a user must wait +thirty minutes \(1800 seconds\) before attempting another login. During this period, all Web administration interface login attempts by the user are refused, including those using the correct password. @@ -28,30 +28,28 @@ This behavior is controlled by the lockout\_retries parameter and the lockout\_seconds service parameter. To review their current values, use the :command:`system service-parameter-list` command. -You can change the duration of the lockout using the following CLI command: +You can change the duration of the lockout using the following |CLI| command: .. code-block:: none - ~(keystone_admin)]$ system service-parameter-modify horizon auth \ - lockout_seconds= + ~(keystone_admin)]$ system service-parameter-modify identity security_compliance lockout_seconds= -where is the time in seconds. +where ```` is the time in seconds. You can change the number of allowed retries before a lockout is imposed -using the following CLI command: +using the following |CLI| command: .. code-block:: none - ~(keystone_admin)]$ system service-parameter-modify horizon auth \ - lockout_retries= + ~(keystone_admin)]$ system service-parameter-modify identity security_compliance lockout_retries= -where is the number of allowed retries. +where ```` is the number of allowed retries. For the changes to take effect, you must apply them: .. code-block:: none - ~(keystone_admin)]$ system service-parameter-apply horizon + ~(keystone_admin)]$ system service-parameter-apply identity Allow about 30 seconds after applying the changes for the Web service to restart.