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.

Description of problem:
Simple bind hangs after enabling password policy

Version-Release number of selected component (if applicable):
# rpm -q 389-ds-base
389-ds-base-1.2.11.15-43.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Turn on the password policy using ldapmodify with following:
    dn: cn=config
    changetype: modify
    add: passwordExp
    passwordExp: on
    -
    add: passwordMaxAge
    passwordMaxAge: 86400
    -
    add: passwordWarning
    passwordWarning: 86400

2. Add a user in ldap server e.g. ppuser1 in my case.

3. ldapsearch -H ldap://<ldapserver> -D uid=ppuser1,ou=People,dc=example,dc=com -w Secret123 -b uid=ppuser1,ou=People,dc=example,dc=com

Actual results:
Search hangs

Expected results:


Additional info:
This is a regression since this was working fine with the 389-ds in rhel6.5

Hi Kaushik, Can you see whether the same works with the previous build of 389-ds-base-1.2.11.15-42?

This bug was introduced by the patch for  Ticket #47748 - Simultaneous adding a user and binding as the user could fail in the password policy check.

There's a corresponding bug for rhel-6.6.
https://bugzilla.redhat.com/show_bug.cgi?id=1079098
Bug 1079098 - Simultaneous adding a user and binding as the user could fail in the password policy check

So, closing this bug as a dup of 1079098, and reopening it.

*** This bug has been marked as a duplicate of bug 1079098 ***

Seems like the issue is fixed in 1.2.11.15-44.el6