starlingx/docs
Code Issues Proposed changes

Fix formatting

Browse Source 
Correct indentation in note.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Idbfca945b6007abb0becdc506522ef0d9e7b618f
This commit is contained in:
Ron Stone 2022-12-20 07:12:05 -05:00
parent 6fe81edbcd
commit cb67e1c0dc
1 changed files with 14 additions and 14 deletions

28
doc/source/security/kubernetes/local-ldap-linux-user-accounts.rst

@ -52,26 +52,26 @@ Local |LDAP| user accounts share the following set of attributes:
This delay is 3 seconds.
You are alerted on the 6th and subsequent attempts:
You are alerted on the 6th and subsequent attempts:
``Account locked due to 6 failed logins``
``Account locked due to 6 failed logins``
and an error message is displayed on subsequent attempts:
and an error message is displayed on subsequent attempts.
When you login to the console you are alerted on the 6th, and
subsequent attempts:
When you login to the console you are alerted on the 6th, and subsequent
attempts:
``The account is locked due to 5 failed logins (2 minutes left to unlock)``
``The account is locked due to 5 failed logins (2 minutes left to unlock)``
When you login remotely using SSH, you have 3 attempts to try
and login before an error ``Permission denied (publickey,password)``
is displayed, during an SSH login session. You can continue to login
by starting a new login session, until the user is locked
out after 5 consecutive failed attempts. For security reasons,
there is no reason or error displayed to the user.
When you login remotely using SSH, you have 3 attempts to try and login
before an error ``Permission denied (publickey,password)`` is displayed,
during an SSH login session. You can continue to login by starting a new
login session, until the user is locked out after 5 consecutive failed
attempts. For security reasons, there is no reason or error displayed to
the user.
5 mins after the account is locked, the failed attempts will be
reset and failed attempts re-counted.
5 mins after the account is locked, the failed attempts will be reset
and failed attempts re-counted.
- All authentication attempts are recorded on the file /var/log/auth.log
of the target host.