RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 834060 - passwordMaxFailure should lockout password one sooner - and should be configurable to avoid regressions
Summary: passwordMaxFailure should lockout password one sooner - and should be configu...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.4
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Sankar Ramalingam
URL:
Whiteboard:
: 740527 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-20 18:08 UTC by Nathan Kinder
Modified: 2020-09-13 19:58 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-1.2.11.12-1.el6
Doc Type: Enhancement
Doc Text:
Feature: password policy Reason: To be consistent with other vendor's ldap servers Result (if any): Added new config option to specfiy which behavior you want.
Clone Of:
Environment:
Last Closed: 2013-02-21 08:19:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 183 0 None None None 2020-09-13 19:58:07 UTC
Red Hat Product Errata RHSA-2013:0503 0 normal SHIPPED_LIVE Moderate: 389-ds-base security, bug fix, and enhancement update 2013-02-21 08:18:44 UTC

Description Nathan Kinder 2012-06-20 18:08:18 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/183

https://bugzilla.redhat.com/show_bug.cgi?id=740527

{{{
Description of problem:

The revocation error process is triggered not when maximum number of
tries is reached but the next time after.
This seems to have changed in Sun DS 6 and is considered the right
behaviour and is required by customer applications.

Example: say we configure 3 tries maximum for revocation, the flow is
the following:

1st try: Invalid password
2nd try: Invalid password
3rd try: Invalid password
4th try and next : Revoked password

Version-Release number of selected component (if applicable):
8.2

How reproducible:
Always.

Steps to Reproduce:
1. Define maximum number of login tries to 3
2. Login with wrong password until password is revoked
3.

Actual results:
1st try: Invalid password
2nd try: Invalid password
3rd try: Invalid password
4th try and next : Revoked password



Expected results:
1st try: Invalid password
2nd try: Invalid password
3rd try and next : Revoked password



Additional info:
}}}
Comment 1 Nathan Kinder 2012-06-21 13:59:56 UTC 
*** Bug 740527 has been marked as a duplicate of this bug. ***
Comment 2 RHEL Program Management 2012-07-10 07:10:13 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3 RHEL Program Management 2012-07-10 23:02:07 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 4 Ján Rusnačko 2012-08-14 11:45:02 UTC 
bug834060 in pwpolicy/pwdpolicy.sh
Comment 6 Ján Rusnačko 2012-10-24 11:59:22 UTC 
Steps to verify:

1) Enable password lockout:
ldapmodify -h localhost -p 22222 -D "cn=directory manager" -w password << EOF
dn: cn=config
changetype: modify
replace: passwordLockout
passwordLockout: on
EOF

2) Set password max failure to 3:
ldapmodify -h localhost -p 22222 -D "cn=directory manager" -w password << EOF
dn: cn=config
changetype: modify
replace: passwordMaxFailure 
passwordMaxFailure: 3
EOF

3) Set passwordLegacyPolicy to off:
ldapmodify -h localhost -p 22222 -D "cn=directory manager" -w password << EOF
dn: cn=config
changetype: modify
replace: passwordLegacyPolicy
passwordLegacyPolicy: off
EOF

4) Add user:
ldapmodify -h localhost -p 22222 -D "cn=directory manager" -w password << EOF
dn: $MYDN
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
cn: test user0
sn: user0
givenName: test
userPassword: password
EOF

5) Try to bind 2 times with incorrect password and check that return code is 49:
ldapsearch -h localhost -p 22222 -D "$MYDN" -w "invalidPassword" -b "$BASE" "uid=$MYUID" 
echo $?
49
 $LDAPSEARCH -h $LDAPhost -p $LDAPport -D "$MYDN" -w "invalidPassword" -b "$BASE" "uid=$MYUID" 
echo $?
49

6) Try to bind third time with incorrect password:
 $LDAPSEARCH -h $LDAPhost -p $LDAPport -D "$MYDN" -w "invalidPassword" -b "$BASE" "uid=$MYUID" 
echo $?
19

[jrusnack@dstet 6.0]$ rpm -qa | grep 389
389-ds-base-1.2.11.15-2.el6.x86_64

Verified
Comment 7 errata-xmlrpc 2013-02-21 08:19:33 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0503.html
Note You need to log in before you can comment on or make changes to this bug.