#1671 mmap cache needs update after db changes
Closed: Fixed Opened by simo.

In the nested groups case we use the memberof plugin to make changes db-wise for changing memberships, however this means changes are not reflected in the mmap cache until the mmap entry naturally expires and is refreshed.
Upon db changes we should make a quick search right after the memberof plugin has done it's work (using modifytimestamp ?) and expire any mmap cache entry that has been chahnged in the db.
This will cause th first app that need s the entry to call into sssd and refresh it with proper values.


Simo is working on this.

owner: somebody => simo

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.3

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=881773

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=881773 881773]

  • Fixed in master:
    • 18afc11a02abda49e25450fdcc553a2e8d6d93b4
    • 2fdd57d428e0c38e3ce1f9286337f750727f0e2e
    • 408914f68673f2caa1c82a1a21336fcb7ddd52ef
    • ebba1aa6b9783daa0d530e9f5e307f7be17d3cd3
    • 8088274b2389b76f4be581736e55f26a8322fad1
  • Fixed in sssd-1-9:
    • b9d9832829aae62aed1a4f76abf2f88d25133dca
    • 593ed7196a976c22b123c2d80c490ab69c6a0b33
    • d2282b42c9e2381fa0652479ca00621dc59e1771
    • 535e5ce8fc6594207aa72da245524c1cfcb1280e
    • f1d38d5d0f64940a0c364b84e61137168bc23cf9

patch: 0 => 1
resolution: => fixed
status: new => closed

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

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

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