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.
Description of problem:
sss_cache -E command invalidates all the user entries in main sysdb cache and timestamp cache, however the group entry in sysdb main cache is unaffected. sss_cache invalidates only the timestamp cache group entries.
Version-Release number of selected component (if applicable):
sssd-1.14.0-34.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Setup 389-ds ldap server and add a test group to it.
2. Setup Rhel-7.3 with SSSD client against LDAP provider.
Sample sssd.conf :
---------------------------------------------
[sssd]
config_file_version = 2
domains = LDAP
services = nss, pam
[domain/LDAP]
id_provider = ldap
auth_provider = ldap
debug_level = 0xFFF0
cache_credentials = FALSE
ldap_uri = ldaps://<LDAP_SERVER>
ldap_tls_cacert = /etc/openldap/certs/cacert.asc
ldap_search_base = dc=example,dc=com
3. Run a group lookup.
# getent group "Group R A"
Group R A:*:111000:
4. Try to expire the group record.
# sss_cache -E
5. Run ldbsearch and verify the dataExpireTimestamp in main sysdb (cache_LDAP.ldb).
# ldbsearch -H cache_LDAP.ldb -b "name=Group R A@ldap,cn=groups,cn=LDAP,cn=sysdb" | grep dataExpireTimestamp
asq: Unable to register control with rootdse!
dataExpireTimestamp: 1473107970
6. Run ldbsearch and verify the dataExpireTimestamp in time stamp cache.
# ldbsearch -H timestamps_LDAP.ldb -b "name=Group R A@ldap,cn=groups,cn=LDAP,cn=sysdb" | grep dataExpireTimestamp
dataExpireTimestamp: 1
Actual results:
dataExpireTimestamp in sysdb main cache is not set to 1 (or its not invalidated).
Expected results:
dataExpireTimestamp in sysdb main cache should be set to 1 for the group entries like other user entries in the cache.
Additional info: