 | Under Construction This proposal is under construction and is not ready for review. |
Zend Framework: Zend_Acl Component Proposal
| Proposed Component Name | Zend_Acl |
|---|---|
| Developer Notes | http://framework.zend.com/wiki/display/ZFDEV/Zend_Acl |
| Proposers | Aleksey V. Zapparov |
| Revision | 0.1 - 22 April 2008: Initial release (explanation of idea). (wiki revision: 3) |
Table of Contents
1. Overview
Improvement of Zend_Acl, so it will become multi-model (not limited to RBAC model as right now).
2. References
3. Component Requirements, Constraints, and Acceptance Criteria
Not defined yet.
4. Dependencies on Other Framework Components
No dependecies.
5. Theory of Operation
I propose not to limit ACL to the only RBAC model. There are a lot of models. And all of them are just a bases, so in certain project developer creating a new model based on ideas of well-known models.
I agree that RBAC is very good model and t can be used almost in all cases, but don't forget about almost. So for example right now a I need an ACL model based on ideas of bit field. Of course it can be done with RBAC, but with additional classes and functions.
6. Milestones / Tasks
Not ready yet.
7. Class Index
- Zend_Acl
8. Use Cases
| UC-01 |
|---|
9. Class Skeletons
Labels:
None
4 Comments
comments.show.hideAug 16, 2008
Tobias Gies
Hi Aleksey,
right now, it seems to be a bit hard to grasp what exactly you mean by different "models". It could certainly help if you could add some Wikipedia links (for example) for RBAC and LBAC.
Best regards
Tobias
Oct 31, 2008
Matthew Ratzloff
The name of this proposal should reflect what it's about: "Zend_Acl Improvements"
Sep 23, 2010
Martin Keckeis
The ACL would also need a hierarchie.
Often a user has rights for one department and for another not (or groups...)
Feb 05, 2011
Dolf Schimmel (Freeaqingme)
Archiving this proposal, feel free to recover it when you want to work on it again. For more details see this email.