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.
DescriptionNikolai Kondrashov
2013-01-02 17:14:03 UTC
Description of problem:
Smart refresh doesn't notice a newly added "defaults" entry with OpenLDAP server. It gets noticed only after full refresh.
Version-Release number of selected component (if applicable):
libsss_idmap-1.9.2-59.el6.x86_64
sssd-client-1.9.2-59.el6.x86_64
sudo-1.8.6p3-6.el6.x86_64
sssd-1.9.2-59.el6.x86_64
libsss_sudo-1.9.2-59.el6.x86_64
openldap-servers-2.4.23-31.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. Use the attached sudo_defaults_openldap_test.ldif file to fill LDAP directory.
2. Use the attached sssd.conf as the base for SSSD configuration.
3. Execute the attached sudo_defaults_openldap_test script as root after modifying it to connect to the LDAP server.
Actual results:
sudo: no tty present and no askpass program specified
initially: 1
sudo: no tty present and no askpass program specified
smart_refresh_with_rule_added: 1
sudo: no tty present and no askpass program specified
smart_refresh_with_defaults_added: 1
full_refresh_with_defaults_added: 0
Expected results:
sudo: no tty present and no askpass program specified
initially: 1
sudo: no tty present and no askpass program specified
smart_refresh_with_rule_added: 1
smart_refresh_with_defaults_added: 0
full_refresh_with_defaults_added: 0
Additional info:
This works with sssd sudo backend and 389-ds and with LDAP sudo backend and OpenLDAP server.
Comment 1Nikolai Kondrashov
2013-01-02 17:16:27 UTC
I managed to reproduce this issue. The problem is that OpenLDAP check whether the filter contains schema-correct value for modifyTimestamp attribute.
We use modifyTimestamp>=0 in smart refresh filter in case USN values are not available. OpenLDAP rejects this filter and returns 0 records. The correct value to use would be 000101010000Z.
I'll prepare a patch.
Comment 12Nikolai Kondrashov
2013-01-11 19:17:03 UTC
Verified fixed with the following packages:
sssd-client-1.9.2-68.el6.x86_64
libsss_sudo-1.9.2-68.el6.x86_64
sudo-1.8.6p3-6.el6.x86_64
libsss_idmap-1.9.2-68.el6.x86_64
sssd-1.9.2-68.el6.x86_64
Relevant sudo suite output:
:: [ PASS ] :: defaults_with
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-0508.html