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:
When exception ldap.INVALID_CREDENTIALS is raised during user bind, the response controls are not returned. 
Response controls should be attached also to unsuccessful response messages.
We are blocked by this issue when creating automated tests and we need it resolved.

Version-Release number of selected component (if applicable):
python-ldap 3.2.0


How reproducible:
Always

Steps to Reproduce:
1. Enable password policy
2. Set a non-zero value to pwdMaxAge and userPassword to pwdAttribute of password policy ldap entry
3. Create user with password attribute
4. Let the password expire
5. Use LDAPObject.simple_bind() on the user (which raises ldap.INVALID_CREDENTIALS)

Actual results:
Response controls are not returned.

Expected results:
Response controls should be attached also to unsuccessful response messages.

Additional info:
An issue has been already created some time ago and fix was presented but not merged.
https://github.com/python-ldap/python-ldap/issues/208

The problem will be fixed by python-ldap-3.3.1-1.el8 rebase.

The upstream bugfix comes with a test case that is automatically run on package build. Additional testing is not needed.

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 (python-ldap bug fix and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2021:1776