SSSD / sssd

#250 enumeration updates using modifyTimestamp not ok in mmr environments
Closed: Invalid Opened by simo.

Closed: Invalid
Reopen Issue

When multi-master in use modifyTimestamp based searches are not enough to guarantee you'll get all latest entries. This is because 2 masters can race and you can get "older" entries in the server you are asking for updates after a more recent change happened in it.

Against 389 DS entryCSN can be used but it is valid only locally per-server (AD has a similar attribute also valid only locally).

We need to make the attribute we check for configurable, and also do a full enumeration if we connect to a different server.

Fields changed

owner: somebody => simo

Fields changed

rhbz: => 0

This ticket was filed over 7 years ago and we already do a full enumeration in case we switch to a new server, so I think this ticket is OK to be closed.

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: => 0
patch: => 0
review: => 1
selected: =>
sensitive: => 0

Fields changed

component: SSSD => Local Provider

Closing, see comment #3 for explanation.

resolution: => wontfix
status: new => closed

Metadata Update from @simo:
- Issue assigned to simo
- Issue set to the milestone: SSSD Patches welcome

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/1292

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.
Metadata
None
None
None
Normal
defect
Local Provider
master
0
0
0
0
0
1
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.