Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause: SSSD did not keep a copy of the list of supported LDAP controls during the whole LDAP operation. At the same time, it used the list of controls to determine if password expiration controls were available
Consequence: Password expiration warnings did not work because SSSD thought they were not available
Fix: SSSD always requests the expiration controls and only acts upon the controls actually being created or not.
Result: Password expiration warnings are displayed
Created attachment 515750[details]
sssd debug logs
Description of problem:
sssd forgets about the supportedControls retrieved from the rootDSE.
Version-Release number of selected component (if applicable):
sssd-1.5.1-34.el6.2.x86_64
How reproducible:
setup a ldap server with server-side password controls.
Steps to Reproduce:
1. setup 389-ds w/server-side pw controls
2. create an account and set the password
3. change the expiration date to within the expiration warning period
4. turn sssd debugging way up
Actual results:
see attached log
Expected results:
things like password expiration warnings should work
Additional info:
irc.freenode.net/#sssd:
<roysjosh> hello all. I'm having some trouble with LDAP server-side password policy. with debugging on, I get: [sdap_control_create] (3): Server does not support the requested control [1.3.6.1.4.1.42.2.27.8.5.1]. but a search of supportedControls on the rootDSE shows this control. this means that I don't get warnings when passwords are about to expire, etc.
<roysjosh> and further debugging shows sssd getting that control: [sdap_set_rootdse_supported_lists] (1): 10 : 1.3.6.1.4.1.42.2.27.8.5.1
<roysjosh> sssd-1.5.1-34.el6.2, by the way
<roysjosh> also, for a possible future enhancement, 389-ds returns a control for expiration notification that sssd doesn't handle: [simple_bind_done] (9): Server returned control [2.16.840.1.113730.3.4.5].
<roysjosh> I don't think the supported controls are ever copied from the main connection to the binding connection...?
<roysjosh> I also have debugging in the loop in sdap_check_sup_list which doesn't print out anything
<sgallagh> sdap_connect_send() is *supposed* to re-request the RootDSE, I think.
<sgallagh> Let me check
<roysjosh> sdap_cli_connect_send does
<roysjosh> sgallagh, ^
<sgallagh> Ahh, ok.
<sgallagh> I see the problem, then.
<sgallagh> You're right, we should be either re-requesting the RootDSE or copying it from the original connection.
<sgallagh> roysjosh: Please file a Bugzilla with this information and we'll get it fixed.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: SSSD did not keep a copy of the list of supported LDAP controls during the whole LDAP operation. At the same time, it used the list of controls to determine if password expiration controls were available
Consequence: Password expiration warnings did not work because SSSD thought they were not available
Fix: SSSD always requests the expiration controls and only acts upon the controls actually being created or not.
Result: Password expiration warnings are displayed
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/RHBA-2011-1529.html
Created attachment 515750 [details] sssd debug logs Description of problem: sssd forgets about the supportedControls retrieved from the rootDSE. Version-Release number of selected component (if applicable): sssd-1.5.1-34.el6.2.x86_64 How reproducible: setup a ldap server with server-side password controls. Steps to Reproduce: 1. setup 389-ds w/server-side pw controls 2. create an account and set the password 3. change the expiration date to within the expiration warning period 4. turn sssd debugging way up Actual results: see attached log Expected results: things like password expiration warnings should work Additional info: irc.freenode.net/#sssd: <roysjosh> hello all. I'm having some trouble with LDAP server-side password policy. with debugging on, I get: [sdap_control_create] (3): Server does not support the requested control [1.3.6.1.4.1.42.2.27.8.5.1]. but a search of supportedControls on the rootDSE shows this control. this means that I don't get warnings when passwords are about to expire, etc. <roysjosh> and further debugging shows sssd getting that control: [sdap_set_rootdse_supported_lists] (1): 10 : 1.3.6.1.4.1.42.2.27.8.5.1 <roysjosh> sssd-1.5.1-34.el6.2, by the way <roysjosh> also, for a possible future enhancement, 389-ds returns a control for expiration notification that sssd doesn't handle: [simple_bind_done] (9): Server returned control [2.16.840.1.113730.3.4.5]. <roysjosh> I don't think the supported controls are ever copied from the main connection to the binding connection...? <roysjosh> I also have debugging in the loop in sdap_check_sup_list which doesn't print out anything <sgallagh> sdap_connect_send() is *supposed* to re-request the RootDSE, I think. <sgallagh> Let me check <roysjosh> sdap_cli_connect_send does <roysjosh> sgallagh, ^ <sgallagh> Ahh, ok. <sgallagh> I see the problem, then. <sgallagh> You're right, we should be either re-requesting the RootDSE or copying it from the original connection. <sgallagh> roysjosh: Please file a Bugzilla with this information and we'll get it fixed.