Bug 37416 - Samba ADDC: badPwdCount not reset directly after unlock
Samba ADDC: badPwdCount not reset directly after unlock
Status: RESOLVED WORKSFORME
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 4.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: Arvid Requate
http://technet.microsoft.com/en-us/li...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-12-23 16:02 CET by Arvid Requate
Modified: 2017-04-24 13:33 CEST (History)
0 users

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments
check_samba4_badPwdCount.sh (3.38 KB, text/plain)
2014-12-23 16:02 CET, Arvid Requate
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2014-12-23 16:02:29 CET
Created attachment 6561 [details]
check_samba4_badPwdCount.sh

The attached script shows that the behaviour of the automatic password unlock in Samba AD DC is a little bit unexpected:


When a bad password lockout policy has been configured e.g. via

  samba-tool domain passwordsettings set \
        --account-lockout-duration=1 \
        --account-lockout-threshold=3

a user account gets locked after three logon failures. After the lockout duration the user may try again. If he then logs on successfully, the badPwdCount of his account gets reset to 0. This works.


The unexpected behaviour is this: If the user doesn't enter a valid password after the lockout duration has passed then the account gets locked immediately again, after just a single failed attempt, and the account is locked again for the lockout duration. This could lead to the impression that the automatic unlock does not work at all.

We should check how AD works in this situation.
Comment 1 Arvid Requate univentionstaff 2014-12-23 16:06:05 CET
The few AD documents I found until now leave room for interpretation. IMHO it would be more consistent to reset the badPwdCount to the value 1 at the first new logon failure after the lockout duration has passed..