Bug 1031074 - [RFE] sss_cache does not povide options to invalidate sudo rules from cache
[RFE] sss_cache does not povide options to invalidate sudo rules from cache
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: SSSD Maintainers
Steeve Goveas
Marc Muehlfeld
: FutureFeature
: 1031073 (view as bug list)
Depends On: 1031073
Blocks: 1113520 1203710 1205796 1296125 1313485
  Show dependency treegraph
Reported: 2013-11-15 09:53 EST by Ron van der Wees
Modified: 2016-11-04 03:09 EDT (History)
14 users (show)

See Also:
Fixed In Version: sssd-1.14.0-0.1.alpha.el7
Doc Type: Enhancement
Doc Text:
New sss_cache option to mark sudo rules as expired This update enhances the "sss_cache" command from the System Security Services Daemon (SSSD). The options "-r" and "-R" have been added to mark one or all *sudo* rules as expired. This enables the administrator to force a refresh of new rules on the next *sudo* lookup. Please note that the *sudo* rules are refreshed using a different algorithm than the user and group entities. For more information about the mechanism, see the sssd-sudo(5) man page.
Story Points: ---
Clone Of: 1031073
Last Closed: 2016-11-04 03:09:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ron van der Wees 2013-11-15 09:53:44 EST
+++ This bug was initially created as a clone of Bug #1031073 +++

Description of problem:
The sss_cache utility performs cleanups of the SSSD cache. Currently there is no option to clear the cached sudo rules.

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

How reproducible:

Steps to Reproduce:
1. Configure IPA server and add sudo rules
2. Configure SSSD client and enable sudo caching as per the RHEL-6 Identity
   Management guide as found at:
3. Use sudo to cache some rules
4. Check the cache with
ldbsearch -H /var/lib/sss/db/cache_<domain>.ldb \
  -b cn=sudorules,cn=custom,cn=LDAP,cn=sysdb
5. Invalidate the cached sudo rules with sss_cache

Actual results:
The sss_cache utility does not have options to invalidate the sudo rules.

Expected results:
Same as with for example users and groups, be able to invalidate the cached
sudo rules with sss_cache.

Additional info:
Upstream ticket: https://fedorahosted.org/sssd/ticket/2081
Comment 1 Ron van der Wees 2013-11-15 09:54:28 EST
Cloned for RHEL-7
Comment 2 Jakub Hrozek 2013-11-15 10:06:30 EST
Hi, we are aware of this shortcoming but it's not as easy as it sounds due to the way the sudo rules are cached and refreshed. I'm going to link this bug to the upstream ticket. It's very unlikely the RFE is going to happen before 7.1
Comment 3 Jakub Hrozek 2013-11-15 10:06:55 EST
Upstream ticket:
Comment 4 Jakub Hrozek 2013-12-03 08:23:29 EST
*** Bug 1031073 has been marked as a duplicate of this bug. ***
Comment 6 gagriogi 2016-02-09 03:18:34 EST

Do we know if this can be implemented in 7.3?
Comment 7 Jakub Hrozek 2016-02-09 03:39:52 EST
Yes, some prep work already started.
Comment 9 Lukas Slebodnik 2016-04-20 14:30:05 EDT
* fd3cbf6bfe86a245d7e90d2a355794eb9c70d525
* be6d25ea38ddda232175aab5e297d8c6cb223551
* 27a7dedb0ee4d4b51ca4c196aa894ad30cb3e821
* e2d26e97d62f06f65e8228b28746471cc5f73fe5
Comment 13 shridhar 2016-09-06 05:55:44 EDT
Verified with  
~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.3 Beta (Maipo)

~]# rpm -qa|grep sss

1. Invalidate particular sudo rule cache
* Check sssd sudo cache:
   # ~]# ldbsearch -H /var/lib/sss/db/cache_default.ldb -b 'cn=sudorules,cn=custom,cn=default,cn=sysdb' 'name=testuser' dataExpireTimestamp
        # record 1
	dn: name=testuser,cn=sudorules,cn=custom,cn=default,cn=sysdb
	dataExpireTimestamp: 1472807723

	# returned 1 records
	# 1 entries
	# 0 referrals
*. Invalidate the sudo cache of single sudo rule:
   # sss_cache -r testuser
*. Check the sssd_sudo cache of invalidated particular rule
	~]# ldbsearch -H /var/lib/sss/db/cache_default.ldb -b 'cn=sudorules,cn=custom,cn=default,cn=sysdb' 'name=testuser' dataExpireTimestamp
	asq: Unable to register control with rootdse!
	# record 1
	dn: name=testuser,cn=sudorules,cn=custom,cn=default,cn=sysdb
	dataExpireTimestamp: 1

	# returned 1 records
	# 1 entries
	# 0 referrals

Test 2: Invalidate all sudo rule entries from cache

* Check existing valid sudo rules from cache
~]# ldbsearch -H /var/lib/sss/db/cache_default.ldb -b 'cn=sudorules,cn=custom,cn=default,cn=sysdb' '(!(dataExpireTimestamp=1))' name dataExpireTimestamp
# record 1
dn: name=testuser322028,cn=sudorules,cn=custom,cn=default,cn=sysdb
dataExpireTimestamp: 1473159626
name: testuser322028
# record 5000
dn: name=testuser459,cn=sudorules,cn=custom,cn=default,cn=sysdb
dataExpireTimestamp: 1473153336
name: testuser459

# returned 5000 records
# 5000 entries
# 0 referrals

* Invalidate all sudo rules from cache
~]# sss_cache -R
 ~]# ldbsearch -H /var/lib/sss/db/cache_default.ldb -b 'cn=sudorules,cn=custom,cn=default,cn=sysdb' '(!(dataExpireTimestamp=1))' name dataExpireTimestamp
asq: Unable to register control with rootdse!
# record 1
dn: cn=sudorules,cn=custom,cn=default,cn=sysdb

# returned 1 records
# 1 entries
# 0 referrals


~]# ldbsearch -H /var/lib/sss/db/cache_default.ldb -b 'cn=sudorules,cn=custom,cn=default,cn=sysdb' '(dataExpireTimestamp=1)' name dataExpireTimestamp

# record 1
dn: name=testuser316041,cn=sudorules,cn=custom,cn=default,cn=sysdb
name: testuser316041
dataExpireTimestamp: 1
# record 5000
dn: name=root,cn=sudorules,cn=custom,cn=default,cn=sysdb
name: root
dataExpireTimestamp: 1

# returned 5000 records
# 5000 entries
# 0 referrals
Comment 15 errata-xmlrpc 2016-11-04 03:09:51 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.