[MAGNOLIA-2587] AccessManager: streamline WorkspaceAccessUtil so that one can start to use custom AccessManager (per workspace) Created: 26/Jan/09 Updated: 23/Jan/13 Resolved: 26/Jan/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.0 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
This is only a very first step into a better and more flexible security architecture. Something we might target with 4.1. |
| Comments |
| Comment by Philipp Bracher [ 26/Jan/09 ] |
|
It is now possible to subclass WorkspaceAccessUtility and override createAccessManager(acls, repo, workspace). This will allow more complex security behaviors: acls based on node type, write a single page only, proper multi site support, ... |