| Summary | Kolab fails to support group acls |
| Queue | Kolab |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | stuart (at) |
| Requester | csacca (at) thecsl (dot) org |
| Created | 07/14/2005 (7255 days ago) |
| Due | |
| Updated | 07/17/2006 (6887 days ago) |
| Assigned | 07/15/2005 (7254 days ago) |
| Resolved | 07/17/2006 (6887 days ago) |
| Milestone | |
| Patch | Yes |
State ⇒ Resolved
Queue ⇒ Kolab
checking in to see if I can give any help...
State ⇒ Assigned
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Kolab fails to support group acls
Queue ⇒ Horde Framework Packages
New Attachment: kolab_group_perm.patch
State ⇒ Unconfirmed
framework/Kolab/Kolab.php, it's clear that the kolab driver does not
support group acls. This is probably not the right thing to do as
Kolab does support group acls and with the development ldap group
backend, it would be good to support it. I made a patch that check to
see if the acl is for a group or a user, and in the case of a group,
expands the group into a list of users, each having the permissions of
the group. I'm not sure if this is the best way, but it's at the very
least a starting point.
I tested this with a pached ldap group backend, though it is useing
the group API, so it should work fine with the datatree backend.