[Kolab-devel] [issue3544] Cached xfb access not up to date for changed distribution lists

[Thomas Arendsen Hein]

New submission from Thomas Arendsen Hein <thomas at intevation.de>:

When testing kolab/issue3537 (Allowing xfb access to groups does not work)
in nearly Kolab Server 2.2.1 I noticed the following:

If a calendar folder allows (p)xfb access to a group, this generally works now
since the client changing the annotation has to trigger the folder.
But when users are added to or removed from the distribution list, the
corresponding folders are not triggered.

My test:
- created user at example.com, first at example.com, second at example.com
- created a distribution list dl at example.com and added first at example.com to it
- added some events to user at example.com's Calendar folder
- enabled xfb access for dl at example.com to the folder Calendar via the web client
- curl -k -u first at example.com
'https://kolab.example.com/freebusy/user%40example.com.xfb'
  (yields f/b list with X-UID, X-SUMMARY and X-LOCATION -> GOOD)
- curl -k -u seconds at example.com
'https://kolab.example.com/freebusy/user%40example.com.xfb'
  (yields simple f/b list -> GOOD)

- Now add second at example.com to and remove first at example from dl at example.com
- curl -k -u first at example.com
'https://kolab.example.com/freebusy/user%40example.com.xfb'
  (still yields f/b list with X-UID, X-SUMMARY and X-LOCATION -> BAD)
- curl -k -u seconds at example.com
'https://kolab.example.com/freebusy/user%40example.com.xfb'
  (still yields simple f/b list -> BAD)

I do not think that kolabd should trigger all relevant folders when a
distribution list changes, but instead the cache format should not cache
"first at example.com has access", but instead "dl at example.com has access".

----------
assignedto: wrobel
messages: 19528
nosy: martin, thomas, wilde, wrobel
priority: urgent
status: unread
title: Cached xfb access not up to date for changed distribution lists
topic: freebusy, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3544>
___________________________________________________