added 389ds password expiration

This commit is contained in:
Roland Gruber 2016-07-21 20:31:40 +02:00
parent 75f7ee43ca
commit d6365d3c1d
3 changed files with 10 additions and 6 deletions

View File

@ -3976,16 +3976,17 @@ mysql> GRANT ALL PRIVILEGES ON lam_cron.* TO 'lam_cron'@'localhost';
</section>
<section>
<title>Locking status for 389ds (LAM Pro)</title>
<title>Account locking for 389ds (LAM Pro)</title>
<para>This module allows you to display if users are locked by 389ds
server. You can also (de)activate users.</para>
server. You can (de)activate your users. The password expiration time
can also be managed.</para>
<para>Requirements: 389ds LDAP server</para>
<para><emphasis role="bold">Configuration</emphasis></para>
<para>Please add the user module "Locking status
<para>Please add the user module "Account locking
(locking389ds)".</para>
<screenshot>
@ -3996,11 +3997,14 @@ mysql&gt; GRANT ALL PRIVILEGES ON lam_cron.* TO 'lam_cron'@'localhost';
</mediaobject>
</screenshot>
<para>This will show the number of failed login attempts and till when
the user is locked by the system.</para>
<para>This will show the password expiration time. You can edit the
value if needed.</para>
<para>If there are any failed login attempts then LAM displays their
number and till when the user is locked by the system.</para>
<para>The limit of failed login attempts and lockout duration is
configured on your server and not within LAM.</para>
configured on your LDAP server and not within LAM.</para>
<screenshot>
<mediaobject>

Binary file not shown.

Before

Width:  |  Height:  |  Size: 54 KiB

After

Width:  |  Height:  |  Size: 40 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 19 KiB

After

Width:  |  Height:  |  Size: 21 KiB