Summary | Impossible to reject all permissions |
Queue | Horde Base |
Queue Version | 3.0.3 |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | ancorgs (at) banot (dot) net |
Created | 02/14/2005 (7527 days ago) |
Due | |
Updated | 03/06/2005 (7507 days ago) |
Assigned | 03/06/2005 (7507 days ago) |
Resolved | 03/06/2005 (7507 days ago) |
Milestone | |
Patch | No |
State ⇒ Rejected
the code model we have and makes it impossible to efficiently check
permissions. This would require an entirely new permissions API and
implementation. You can simply design your hierarchy with subgroups to
do this.
Type ⇒ Enhancement
State ⇒ Feedback
Priority ⇒ 1. Low
State ⇒ Feedback
would require a bunch of changes in the code. Note that we will never
support denying permissions, but as far as I understood your request
you simply want to add an "empty" permission set for one user.
State ⇒ Unconfirmed
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Impossible to reject all permissions
Queue ⇒ Horde Base
user or group to not be able to show, read, alter nor delete.
If none of the 4 checkboxes are marked, the permission is not set so
you must give at least one privilege to the user/group. This way is
impossible to totally reject access from a specific user or group to a
particular module.