[MGNLCT-32] Security setup for content-types Created: 23/Apr/18 Updated: 28/May/18 Resolved: 22/May/18 |
|
| Status: | Closed |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Oanh Thai Hoang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 1.5d | ||
| Time Spent: | 0.5d | ||
| Original Estimate: | 2d | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Content types foundation | ||||||||
| Sprint: | Saigon 145, Saigon 146 | ||||||||
| Story Points: | 5 | ||||||||
| Description |
|
Content-types 0.5 and 0.6 was bringing two roles:
We want to evaluate how to move forward with the security/role setup for custom content types (and ensure a smooth transition if that was used before in Magnolia Cloud). |
| Comments |
| Comment by Ngoc Nguyenthanh [ 14/May/18 ] |
Current implementation
What's next?New implementation need to take care of some aspects as bellow:
So far, we're discussing the JCR security aspects. For other Data Sources they need to have their implementation and customization. TBC |
| Comment by Mikaël Geljić [ 18/May/18 ] |
|
Great research:
|