Dependency Graph
View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002502 | SOGo | Backend Calendar | public | 2013-11-20 15:07 | 2014-02-06 19:25 |
Reporter | ThomasRZ | Assigned To | francis | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Product Version | 2.1.0 | ||||
Target Version | 2.2.0 | Fixed in Version | 2.2.0 | ||
Summary | 0002502: Wrong handling of ACLs on shared calendars with 2 Groups | ||||
Description | This Bug appears when a user shares his calendar to multiple groups with different ACLs. At least one user has to be in 2 Groups. At the moment the rights of a calendar are handled "old-to-new". The Right way must be "specific-to-unspecific". | ||||
Steps To Reproduce | To reproduce this Bug simply do the following:
Normally it should be possible to modify public objects of User "A", although Group-A only grants read-only rights. You can check the other way round just by changing the rights of Group-A to None, save and change them back to PublicViewer. They will appear at the bottom of the ACLs and SOGo will use the PublicModifier of Group-B now. | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2013-11-20 15:07 | ThomasRZ | New Issue | |
2014-02-06 18:56 | francis | Relationship added | duplicate of 0001854 |
2014-02-06 18:56 | francis | Target Version | => 2.2.0 |
2014-02-06 19:25 | francis | Note Added: 0006516 | |
2014-02-06 19:25 | francis | Status | new => resolved |
2014-02-06 19:25 | francis | Fixed in Version | => 2.2.0 |
2014-02-06 19:25 | francis | Resolution | open => fixed |
2014-02-06 19:25 | francis | Assigned To | => francis |