| Summary | Sharing calendars to ldap groups |
| Queue | Horde Framework Packages |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | ben (at) |
| Requester | bcantin (at) kamayo (dot) com |
| Created | 03/17/2006 (7131 days ago) |
| Due | |
| Updated | 04/18/2006 (7099 days ago) |
| Assigned | 03/17/2006 (7131 days ago) |
| Resolved | 04/18/2006 (7099 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
State ⇒ Assigned
Version ⇒ HEAD
Queue ⇒ Horde Framework Packages
for him if using the DataTree Group driver.
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Sharing calendars to ldap groups
Queue ⇒ Kronolith
New Attachment: screenshots.tar.bz2
which are defined into ldap are recognized and can be seen by the
Administrator
into Administration->groups. So I guess the configuration of
authentication and groups in Horde is correct.
The problem is that calendar's permissions - show, see, edit and delete -
accorded to ldap groups seem to have no effect on user's ability to see shared
calendars (I 'm talking about users belonging to such ldap groups...).
My configuration :
Horde 3.1
Kronolith h3 2.1
Openldap 2.2.26-3 (ubuntu package)
Please find enclosed screenshots :
- of my authentication conf
- of my groups conf
- of the groups recognized
- of the permissions accorded.
Apparently, for calendars shared to ldap groups, key perm_default in
horde_datatree_attributes should be set to 6 instead of being set to 0.