#526 Configure entryUSN plugin to allow correct behavior in clients
Closed: Fixed None Opened 13 years ago by simo.

In sssd we "optimize" enumerations by storing the highest modification time found and searching only for entries with a higher modification time in following requests.

This can fail to find new "older" entries replicated after the last fetch.

By providing the entryUSN attribute we allow clients to always search for newer USNs. Because entryUSN is not replicated, replicated entries always get newer numbers even if the modifyTimestamp on the entry is older.

The clients needs only one major change. It needs to keep track of what server it is contacting and discard the highest USN if it changes server, because entryUSNs are not replicated and therefore don't carry any meaningful state between different servers.


Metadata Update from @simo:
- Issue assigned to simo
- Issue set to the milestone: FreeIPA 2.0 - 2010/11

7 years ago

Login to comment on this ticket.

Metadata