diff options
| author | Pavel Březina <pbrezina@redhat.com> | 2012-05-13 21:45:49 +0200 |
|---|---|---|
| committer | Stephen Gallagher <sgallagh@redhat.com> | 2012-06-29 11:37:18 -0400 |
| commit | fc99ea70d735fa4094c450dd52c3503cb23e5f59 (patch) | |
| tree | 4b6740f78c954e61a79e76474dc533be4e20c9b1 /src/responder/sudo/sudosrv_get_sudorules.c | |
| parent | 4684d427e7e10642ceff62128c3d22db87872c4c (diff) | |
| download | sssd-fc99ea70d735fa4094c450dd52c3503cb23e5f59.tar.gz sssd-fc99ea70d735fa4094c450dd52c3503cb23e5f59.tar.xz sssd-fc99ea70d735fa4094c450dd52c3503cb23e5f59.zip | |
sudo ldap provider: notify responder when an expired rule has been deleted
When an expired rule is not present on the server server during specific rule
refresh, the provider will notify the sudo responder that it has been deleted.
Because there is a high probability that some other rules were deleted from
the server as well, we want to remove them from sysdb as soon as possible.
Once the responder is notified, it will schedule an out of band full refresh.
This is issued by responder, because we already have a mechanism that
prohibits creation of similar request (i.e. once the OOB full refresh is
scheduled, there won't be another).
The notification is done by returning:
DP error = DP_ERR_OK, error = ENOENT
Diffstat (limited to 'src/responder/sudo/sudosrv_get_sudorules.c')
0 files changed, 0 insertions, 0 deletions