#160 provider = files - users and groups deleted with shadow utils do not get removed from sssd.ldb
Closed: Duplicate None Opened 14 years ago by jgalipea.

Description[[BR]]
With a provider = files back end configured, no matter what the cache settings are configured to, users and groups that are deleted using shadow utils, do not get removed from the sssd.ldb. New users and groups added using the shadow utils are added to the sssd.ldb. [[BR]]

Configuration[[BR]]

[services]
description =  Local Service Configuration
activeServices = nss, pam
reconnection_retries = 3

[services/nss]
description = NSS Responder Configuration
filterGroups = root
filterUsers = root
debug-level = 4

[services/dp]
description = Data Provider Configuration
debug-level = 4

[services/pam]
description = PAM Responder Configuration

[services/monitor]
description = Service Monitor Configuration

[domains]
description = Domains served by SSSD
domains = FILES

[domains/FILES]
description = Local Files Users and groups domain
EntryCacheTimeout = 1
EnumCacheTimeout = 1
EntryNegativeTimeout = 1
enumerate = TRUE
minId = 500
provider = files

Steps to reproduce[[BR]]
1. add some local users with uid numbers over 500 using the shadow utils[[BR]]
2. install sssd with above configuration[[BR]]
3. search for users[[BR]]
getent -s sss passwd user1000[[BR]]
4. delete the user using shadow utils[[BR]]
userdel -r user1000[[BR]]
5. wait 10 minutes or more if you like and search for users[[BR]]
getent -s sss passwd user1000[[BR]] [[BR]]

EXPECTED:[[BR]]
After cache entry time out, user to no longer be returned by getent -s sss[[BR]]

ACTUAL: [[BR]]
User remains indefinitely in sssd.ldb[[BR]]

Version [[BR]]
sssd-debuginfo-2009090114-0.fc11.i586


I'm thinking that the default cache timeout should be 1s for provider = files - like sgallagh suggested.

milestone: SSSD 1.0 => SSSD 0.6.0
version: 0.5.0 => master

While it was filed earlier, I'm declaring this as a duplicate of Bug #178, since that addresses the larger problem demonstrated in this bug.

resolution: => duplicate
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @jgalipea:
- Issue set to the milestone: SSSD 0.6.0

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1202

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata